Option to define target DB schema
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 3.5k
- Forks
- 219
- PR merge metrics
- No merged PRs in 30d
Description
Hello ,
Thanks for bringing up this exciting data migration tool. Just want to check is there any possibility to define the target schema as well. Since my case schema name is differ in source and target DB'.s
Source - public
Target - schema2
When I am running the below command ..Table is synced in public schema of target db instead of schema2.
pgsync public.table1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the pgsync public.table1 command and how it selects the destination schema. Define how a target schema such as schema2 should be supplied, then verify that the table is synced there instead of the target database's public schema.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, ruby
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100