Support of PostgreSQL schemas

[wuarmin]

It would be an improvement if we can make use of PostgreSQL schemas in rom-sql. Sequel API supports it using the double underscore special notation.

Especially for legacy tables, it would be easier to migrate to rom-sql.

[flash-gordon]

We'll be working on this, the only reason why this isn't here yet is that PG has the search_path setting which allows you to lookup several schemas at once.
https://www.postgresql.org/docs/9.6/static/runtime-config-client.html
You can use it either by providing a proper connection string, like postgres://localhost/rom_sql?search_path=schema1,schema2 or by configuring the connection with a proc, like

rom = ROM.container(:sql, DB_URL, after_connect: -> c { c.execute("set search_path to schema1,schema2") })

[solnic]

ugh sorry I closed it by an accident, re-opened now

[solnic]

Do you want to do this as part of 1.x or 2.0?

[flash-gordon]

I'd go with 2.0, there is a workaround for PG and in Oracle you can create a synonym. Supporting schemas may require some changes which I'd align with automigrations.

[wuarmin]

Hello,
what is the state of this issue? Is it planned to add the schema feature?
Thanks.
Best regards

[alex-lairan]

There is any way I can help with this issue?

All I see that can be problematic is that the schema waits for a symbol and allow Sequel::SQL::QualifiedIdentifier, but the has_many only allow symbol.

Also, the full name of the table is not found with the Sequel::SQL::QualifiedIdentifier.

This works for simple actions.

schema(Sequel::SQL::QualifiedIdentifier.new('x', 'foo'), as: :x_foo)

This does not works because the name is "'x'.'foo'".

schema(:'x.foo'), as: :x_foo)

[flash-gordon]

it will require rom's identifiers to support schemas for a start, then these identifiers have to be used consistently across from and rom-sql. I tried to implement it once but I didn't succeed, it was too much work. Initially, I used search_path but then I ditched it in favor of a single schema.