How can we not infer relation attributes? about rom-sql HOT 3 CLOSED

Right now schemas are used only for writing, ie for commands. But you can override an underlying dataset which keeps a list of columns for SELECTs with

dataset do |relation|
  pk_header = klass.primary_key_header(db, table)
  select(*relation.schema.attributes.keys).order(*pk_header.qualified)
end

This should work, but I didn't test it
You may find useful the default dataset implementation and the bootstrapping code

from rom-sql.

Thanks a lot!

Working snippet in case somebody else needs it someday:

class Users < ROM::Relation[:sql]
  schema :users, infer: false do
    attribute :id, Types::Int.meta(primary_key: true)
    attribute :email, Types::String
  end

  dataset do |relation|
    pk_header = relation.primary_key_header(db, :users)
    select(*relation.schema.attributes.keys).order(*pk_header.qualified)
  end
end

irb(main):003:0> rom.relation(:users)
=> #<Users dataset=#<Sequel::Postgres::Dataset: "SELECT \"id\", \"email\" FROM \"users\" ORDER BY \"users\".\"id\"">>

from rom-sql.

I'd appreciate if somebody could report an issue about using schema attrs
for the default dataset. It's a simple thing to do I believe.

On 8 October 2016 at 9:11:40 AM, Marion Duprey ([email protected])
wrote:

Closed #98 #98.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#98 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAEKmOZ_i5HciRj5UzN3YpqqtyYQFNzks5qx8C8gaJpZM4KRvrK
.

from rom-sql.