RecordVersionSynchroniseSlave doesn't work with blobs and PostgreSQL

[avavdoshin]

RecordVersionSynchroniseSlave doesn't synchronize tables with blob fields if SLAVE db is PostgreSQL (tested with mormot.db.sql.postgres).
It affect only with synchronisation. If i use PostgreSQL on master server, saving blobs works ok. Synchronisation works ok too if slave db is sqlite.

[synopse]

Could you investigate a little and find out what actually happens?

[avavdoshin]

Batch prepared correct, but something happened in BatchSend, i suppose, because i've got error when step-by-step debug "TSqlDBPostgresStatement.ExecutePrepared: Invalid array type ftBlob on bound parameter #3" (it is one of my blob fields) "in mormot.db.sql.postgres.pas line 656"

[synopse]

Please try with this last commit.

[avavdoshin]

It works now, but only if there is no deleted rows. If i have any deleted row - table doesn't synchronise at all.
Maybe it affected not only tables with blobs, i don't know. In my case i do not delete rows in another tables.

[synopse]

I am not able to reproduce this behavior.

[avavdoshin]

I create some orms on master
Then i created TOrm (1,2,3,4,5,6) with blob on master
Then delete record 4 with blob on master
then create some other orms on master

Then synchronise from master (sqlite) to slave (postgresql) (calling RecordVersionSynchroniseSlave from slave).
Nothing synchronised for TOrm (where i delete record), other orms synchronised well .

If i only create TOrm on master (do not delete) - synchronise works ok

[avavdoshin]

In step-by-step debug i've got error
"Unexpected TSqlDBPostgresConnectionProperties.SharedTransaction (1,2)" in mormot.db.sql line 3701

Maybe it's because in prepared for sending batch i see in JSON that DELETE goes before all other lines? But this record cannot be deleted, it doesn't exist on slave server yet.

[avavdoshin]

fails on TRestOrmServerBatchSend.AutomaticCommit after sequence POST-POST-POST-POST-DELETE-POST if ID for delete doesn't exists. Can't find out reason yet. No error message except "TSqlDBPostgresConnectionProperties.SharedTransaction( )"

upd: If i comment whole part for encDelete in TRestOrmServerBatchSend.ExecuteValue it fails too with the same exception

[synopse]

Sorry for the late reaction.

What does "if ID for delete does not exist" mean in your case?

[avavdoshin]

Sorry for the late reaction.

What does "if ID for delete does not exist" mean in your case?

I mean that record was deleted only on master db, it doesn't exist on slave db (sync was made after modifications on master db as i wrote before)
But when synchronization starts it tries to delete record which doesn't exist on slave db.
I suppose it's because of different transactions in post and delete chains