PostgreSQL Specific Features
Last updated
Was this helpful?
Last updated
Was this helpful?
Earlier we described the engine-independent features of .
The default select()
call (as all other Ent API calls) is generic and engine independent, be it PostgreSQL or any other database. In addition to that, select()
allows to pass the last optional engine-specific argument, to let you use the most of PostgreSQL features without falling back to vanilla SQL queries prematurely.
Despite the last optional parameter is an untyped object, it in fact accepts the following structure:
An artificial usage example:
Of course, this all works only within one microshard. You can't use JOINS or WITH statements targeting different microshards.
Continue reading: Query Planner Hints.