PG::AmbiguousColumn: ERROR: column reference is ambiguous

[AmitLamichhane2021]

Hi Team,
I am trying to use custom ordering via the order_by property and I am running into a "column reference is ambiguous" error. The column I am trying to order by is called created_at.
My pagination query joins to multiple tables that all have a created_at column, so that column name is ambiguous if used by itself. I get the following error when trying to paginate with a cursor:
block in tagged - PG::AmbiguousColumn: ERROR: column reference "created_at" is ambiguous
It seems like the gem isn't appending the table name to custom order_by columns, is this the case?

[modosc]

it looks like a fork has a fix for this: frollous@efc9a15#diff-c201f4d60dd83e98535d880e8d9b9ad479792383bb84e0cddd4a9122514e11b5

i'm testing it now in our application. i tried making a pr with this change + specs but i cannot get the specs running locally on my machine (the combination of ruby 3.0.6 + mysql2 won't build on my mac?)

[jeremyhaile]

I'm running into this - any update?

[AmitLamichhane2021]

@jeremyhaile I created the fork to fix the issue and it is working well.

[jeremyhaile]

@AmitLamichhane2021 thanks for that. Unfortunately I need it to be based on 0.4+ as there are other bugfixes I depend on. It'd be nice if we could get a PR for your patch, which looks like a no-brainer change!

If you don't have time, I'll see if I'm able to get specs running locally and try to open one against the latest version.