Closed ka-ramba closed 2 years ago
I see multiple (related) issues to that:
"another_schema.table_name"
, it doesn't generate the expected CREATE TABLE another_schema.table_name...
but CREATE TABLE "another_schema.table_name"...
.search_path
. Having the suggested option to select the schema at connection could be useful, but maybe not sufficient for many applications.another_schema.table_name
. The issue for extending the protocol I can see is that, schema
is used for the table name. Adding another entry that relates to the schema will be confusing...If anybody has a good idea on how we could (safely!) bypass the escaping of names on the SQL requests, I would be happy to look at it :-)
Right now all connections happen to go to the 'public' schema, which is a showstopper in many production environments. I think the Postgres connection string has search_path