Any option to define destination db's schema?

[saytesnake]

Is your feature request related to a problem?

Well, in some dev env, sometimes the db's schema is different, not just "public".

Describe the solution you'd like

Just like source db's public.aaa1 sync to destination db's abc.aaa1。

Describe alternatives you've considered

Table to table with mapping, just like source db's public.aaa1 sync to destination db's public.bbb1? Not sure if it's a good idea.

Thx !

[nickzelei]

Hi there! Thanks for the feature request. This is something we have considered. It's not on our immediate roadmap, but is something we'd like to see added to Neosync eventually!

There are definitely a few different usecases here that I can think of:

1. Schema Migration. (highlighted above). -- When you want to move all or some of your tables from one schema to another.
2. Table Migration. -- When you want to move your data from one table to another

[nickzelei]

@saytesnake Can you tell me more about your immediate need/usecase? Is it that in production/some env your tables are in X schema but in development you have them in Y schema?