core: Postgres error halts / corrupts syncing from block 98475 related to DAO TransferRestrictionStatus

During Postgres sync with the last Postgres Dao updates got this error:

server.go:1147] Server._handleBlock: Received block ( 98475 / 98627 ) from Peer [ Remote Address: 34.123.41.111:17000 PeerID=32 ] E0126 08:54:21.794215 1 server.go:1141] Server._handleBlock: Encountered an error processing block <Header: < 98475, 00000000000058e8268e3ca270ab453fdd41382623c5ca30516d6ddf95b7b764, 1 >, Signer Key: BC1YLh768bVj2R3QpSiduxcvn7ipxF3L3XHsabZYtCGtsinUnNrZvNN>. Disconnecting from peer [ Remote Address: 34.123.41.111:17000 PeerID=32 ]: Error while processing block: : ProcessBlock: Problem upserting block and transactions: ERROR #23502 null value in column "transfer_restriction_status" violates not-null constraint

Seem related to Dao coin insert/update at first glance. Related to DAOCoinTransferRestrictionStatus TransferRestrictionStatus pg:"dao_coin_transfer_restriction_status"

When this block hits in the sync all blocks after get status 26 in pg_blocks.

Looking for a solution or fix.

So transfer_restriction_status SMALLINT NOT NULL seems to get a NULL value and rejects that. type PGMetadataDAOCoin struct { tableName struct{} pg:“pg_metadata_dao_coins”`

TransactionHash           *BlockHash           `pg:",pk,type:bytea"`
ProfilePublicKey          []byte               `pg:",type:bytea"`
OperationType             DAOCoinOperationType `pg:",use_zero"`
CoinsToMintNanos          string
CoinsToBurnNanos          string
TransferRestrictionStatus `pg:",use_zero"`

}`

Might be related to pg:",use_zero" for that enum type.

Would transfer_restriction_status SMALLINT NOT NULL with DEFAULT 0 added solve the issue? Took me 2 days to sync to get to that point. Any ideas are welcome.

This PR from @tijno brings us to block 98477 #201 But still seems something goes wrong with the status field