Filter columns in Select about orm HOT 11 CLOSED

Also, I don't see any opportunities to extend this library on my side, and this makes me very sad. (( Can I refactor it and make customization much easier (I think so, at least =) )?

from orm.

Hi, I will be able to respond in more details after new year eve holidays (our company is off this time). Getting model with partial fields can open a lot of issues in your business logic so we left columns() not reachable intentionally. But, have you checked embedded models? They can be lazy loaded which essentially can be used as safe way to achieve partial loading.

from orm.

https://cycle-orm.dev/docs/relation-embedded#eager-and-lazy-loading

from orm.

Unfortunately, embedded entities is not that I want to. ((

In my company we try to build JSON API request parser (like in jsonapi.org) and we need to dynamically choose field getting from database (fields=field1,field2&fields[related_entity]=field2) for some issues in our business logic.

from orm.

Hmmm; I don’t think such approach lays down well with ORMs but we can make this https://github.com/cycle/orm/blob/master/src/Select/RootLoader.php#L156 to be customizable.

from orm.

You can also init ORM with custom column schema.

from orm.

Hmmm; I don’t think such approach lays down well with ORMs but we can make this https://github.com/cycle/orm/blob/master/src/Select/RootLoader.php#L156 to be customizable.

This is would be great!

from orm.

You can also init ORM with custom column schema.

So, I just can redefine schema, than do some query stuff and after fetchAll() can work with whole entity tree?

from orm.

Correct. You can basically create new ORM instance with specific set of columns, that’s what dynamic schema is doing.

from orm.

Hmmm... But without some changing in SchemaInterface I'm still not able to do some small manual schema customization. =)

from orm.

Schema recreating works at first look, thanks for your response!

from orm.