Please support another schema in target PostgreSQL rather than public

[abrilliantov]

I tried following json

{
 "source": {
   "mode": "convert",
   "type": "mysql",
   "connection": "root:pass@tcp(host.docker.internal:3306)/source_db"
 },
 "target": {
   "type": "postgresql",
   "connection": "postgres://postgres:postgres@host.docker.internal:5432/target_db/target_schema"
 }
}

but got error

target_db/target_schema does not exist

[slotix]

Example DSN

user=postgres password=postgres host=host.docker.internal port=5432 dbname=target_db

Example URL

postgres://postgres:postgres@host.docker.internal:5432/target_db

The connection can be in URL format or keyword = value format (DSN style).

See more at https://stream.dbconvert.com/sources/postgresql/postgresql-server#postgresql-specific-options

It's not possible to specify the schema directly in the connection string, but you can specify the schema inside the filter:

 "source": {
   "mode": "convert",
   "type": "mysql",
   "connection": "root:pass@tcp(host.docker.internal:3306)/source_db",
   "filter": {
      "tables": [
        { "name": "private.products1", "operations": ["insert", "update", "delete"]},
        { "name": "products2", "operations": ["insert", "update", "delete"]}
      ]
    }
 },
 "target": {
   "type": "postgresql",
   "connection": "postgres://postgres:postgres@host.docker.internal:5432/target_db"
 }
}

[abrilliantov]

@slotix so, basically, I need to specify all my 131 tables there in filters ?

That's definitely not appropriate, especially in fast-moving startup environments, where number of tables can grow +-10 each week

[slotix]

@PekopT You're absolutely right. Managing 131 tables individually in filters sounds like a recipe for chaos. We are developing a new version with a simpler approach to specifying PostgreSQL schemas.