Nulls ordering skips records if there is more than one NULL about order_query HOT 6 CLOSED

Thanks for looking into this @glebm , and let me know if I can assist.

from order_query.

After adding a test for multiple nulls, I can see that the query it generates without wrap_top_level_or has an incorrect OR clause:

  SELECT "posts".* FROM "posts"
   WHERE ("posts"."published_at" IS NULL OR -- <- *this is wrong*
          "posts"."published_at" IS NULL AND "posts"."id" < 47)
ORDER BY "posts"."published_at" IS NULL ASC,
         "posts"."published_at" ASC,
         "posts"."id" DESC LIMIT 1

from order_query.

@twelve17 Got a fix here: #22

If it works for you, I'll release a new version.

You can try it out with:

gem 'order_query', git: 'https://github.com/glebm/order_query', branch: 'null-wtlo'

There should be no need to set wrap_top_level_or = false in that branch (it wasn't a sufficient workaround anyway).

from order_query.

Hi @glebm , things seem to work with the updated code. 🎉

I did not use wrap_top_level_or = false for this test (I omitted the setting altogether).

For posterity, here its the resulting query:

seek_args: [[:title, :desc, {:nulls=|:first}]]
Entry Load (1.0ms)  SELECT  `entries`.* FROM `entries` ORDER BY `entries`.`title` IS NULL DESC, `entries`.`title` DESC, `entries`.`id` ASC LIMIT 20
Entry Load (0.7ms)  SELECT  `entries`.* FROM `entries` WHERE `entries`.`id` = 1 LIMIT 1
Entry Load (0.7ms)  SELECT  `entries`.* FROM `entries` WHERE (`entries`.`title` IS NULL AND `entries`.`id` | 1) ORDER BY `entries`.`title` IS NULL ASC, `entries`.`title` ASC, `entries`.`id` DESC LIMIT 1

Thanks for your help with this!

from order_query.

BTW, please feel free to close the other issue, it's obviously less pressing given this is working. Thanks again.

from order_query.

Fix released in v0.4.1

from order_query.