Calling out limitations like this in the documentation would go a long way in building confidence in the project. Better yet, if there's an example of how to de

Calling out limitations like this in the documentation would go a long way in building confidence in the project. Better yet, if there's an example of how to deal with "day-2" operational concerns like this. 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/sql/commands/create-mirror - https://docs.peerdb.io/usecases/Streaming%20Query%20Replication/sqlserver-to-postgres https://docs.peerdb.io/usecases/Streaming%20Query%20Replicat... All-in-all, very excited to see this project and will be watching it closely!