You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generic support for custom FROM clauses would be useful and consistent with other escape hatches like Expr::cust.
It's a bit weird that methods like SelectStatement::from accept an IntoTableRef parameter, where TableRef is a rigid exhaustive enum that doesn't provide any escape hatches. Because of this rigidity, it looks like we'll need a major version bump to introduce an escape hatch.
If a maintainer reads this thread, please create a milestone for sea_query 0.33 and add this issue to that milestone.
Right, I'm working with SQLite so I didn't notice the MySQL hints are already supported. Then maybe would make sense to implement the specialized hints for SQLite as well?
Motivation
Some queries require manually disabling or specifying indexes, which is currently supported with index hints after the table name in the
FROM
clause.See documentation of the support for index hints:
INDEXED BY <index-name>
andNOT INDEXED
: https://www.sqlite.org/syntax/table-or-subquery.htmlFor PostgreSQL I haven't found an equivalent alternative.
Proposed Solutions
I would like to either:
FROM
clauseThe text was updated successfully, but these errors were encountered: