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
I believe this is a hack, but it does produce the desired result. However it results in a cycle in the migration logic of dropping the index and then re-creating it.
I have a query that is frequently run on a large table that has sorting like this:
which translates to SQL like this:
How can I create a database index that includes the
NULLS FIRST
part?Currently I've got:
which produces:
but what I need is:
Alternatively is there a way to include arbitrary SQL after a column when creating a database index?
The text was updated successfully, but these errors were encountered: