When a block reward is spent together with other outputs in the wallet and that block reward is later orphaned, the wallet does not show the other funds as available anymore.  Even a `-rescan` is not enough - only `-zapwallettxes` or an explicit `abandontransaction` "recovers" the funds.  I prepared a [test case](https://github.com/domob1812/bitcoin/blob/wallet-bug-invalidated-block-rewards/test/functional/wallet_bug.py) that shows this behaviour.

Is this a known issue or the expected behaviour?  While this situation is something that will presumably not occur in practice (as it requires a long reorg), I wonder if that transaction should be automatically abandoned as it seems clear it won't be able to be confirmed anymore.
WalletLogPrintf("Could not generate scriptPubKeys (cache is empty)\n");
            return nullptr;
        }
        if (!internal) {
            for (const auto& script  script_pub_keys) {
                CTxDestination dest;
                if (ExtractDestination(script, dest)) {
                    SetAddressBook(dest, label, "receive");
                }
            }
        }
    }
    // Save the  to DB
    spk_man->WriteDescriptor();
    return spk_man;
}
bool CWalletMigrateToSQLite(bilingual_str& error)
{
    AssertLockHeld(cs_);
    WalletLogPrintf("Migrating  storage database from BerkeleyDB to SQLite.\n");
    if (m_database->Format() == "sqlite") {
        error = _("Error This  already uses SQLite");
        return false;
    }
    // Get all of the records for DB type migration
    stdunique_ptr<DatabaseBatch> batch = m_database->MakeBatch();
    stdunique_ptr<DatabaseCursor> cursor = batch->GetNewCursor();
    stdvector<stdpair<SerializeData, SerializeData>> records;
    if (!cursor) {
        error = _("Error Unable to begin reading all records in the database");