What happens if there's a table schema change on a mapped table on the source side? What about on the target side?
For CDC, change stream does give us events in case of schema changes, we would have to replay them on the destination. Schema changes on the destination are not supported, the general recommendation is to build new tables / views and let PeerDB manage the destination table.
For streaming the results of a query, as long as the query itself can execute (say a few columns were added or untouched columns were edited) mirror job will continue to execute. In case this is not the case, there will be some manual intervention needed to account for the schema changes.
Thanks for the question, this is a requested feature and on our roadmap.
Simply looking at the docs on these two pages, its unclear to me whether there's a way to update the mirror definition when a schema change occurs or if I need to drop & recreate the mirror (and what the effects of this are in the destination):
- https://docs.peerdb.io/sql/commands/create-mirror
- https://docs.peerdb.io/usecases/Streaming%20Query%20Replicat...
All-in-all, very excited to see this project and will be watching it closely!