Can you provide an executable test script using this template?

Couldn't recreate the issue. Here is my executable test script, @kamipo ,

https://gist.github.com/Bartuz/175845efab2ab3f3bc6b808cced7f571

@clemthenem , are you sure it isn't something about your applicationRecord?

@Bartuz , the reason your script did not replicate the issue is because your code creates a query but doesn't execute it. If you append a ruby command like "map(&:id)" to the end of your query, then it does reproduce the error.

Using ruby 2.4.2, I was able to replicate the behavior that @clemthenem described by using @Bartuz 's script with ".map(&:class)" appended to the query. I observed different error messages when using the 'pg' gem vs. the 'sqlite3' gem: "PG::UndefinedTable: ERROR: missing FROM-clause entry for table 'profiles_profile_translations'" vs "SQLite3::SQLException: no such column: profiles_profile_translations.id". But both cases logged the same generated SQL to stdout:

> ProfileTranslation.joins(:profile).includes(:user, :profile).map(&:class)
SELECT "profile_translations"."id" AS t0_r0, "profile_translations"."profile_id" AS t0_r1,
  "users"."id" AS t1_r0, "profiles_profile_translations"."id" AS t2_r0,
  "profiles_profile_translations"."user_id" AS t2_r1
  FROM "profile_translations"
  INNER JOIN "profiles" ON "profiles"."id" = "profile_translations"."profile_id"
  LEFT OUTER JOIN "profiles" "profiles_profile_translations_join"
    ON "profiles_profile_translations_join"."id" = "profile_translations"."profile_id"
  LEFT OUTER JOIN "users"
    ON "users"."id" = "profiles_profile_translations_join"."user_id"

And the contrasting example did produce SQL without the phantom table:

> ProfileTranslation.joins(:profile).includes(:profile, :user).map(&:class)
SELECT "profile_translations"."id" AS t0_r0, "profile_translations"."profile_id" AS t0_r1,
  "profiles"."id" AS t1_r0, "profiles"."user_id" AS t1_r1, "users"."id" AS t2_r0
  FROM "profile_translations"
  INNER JOIN "profiles" ON "profiles"."id" = "profile_translations"."profile_id"
  LEFT OUTER JOIN "profiles" "profiles_profile_translations_join"
    ON "profiles_profile_translations_join"."id" = "profile_translations"."profile_id"
  LEFT OUTER JOIN "users"
    ON "users"."id" = "profiles_profile_translations_join"."user_id"

I don't know enough to evaluate @clemthenem 's symptoms, nor whether the example is well-formed.

Hi guys,
Thanks a lot @Bartuz and @houhoulis for your time replicating the issue, I apologise for not replying earlier... The example is well formed yes, that's exactly what happened to me. Let me know if you need any extra info @kamipo and thank you so much for your help!

This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails team are limited, and so we are asking for your help.
If you can still reproduce this error on the 5-1-stable branch or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.

Was this fix released in rails 4 line or only 5.1.x, i am sorry not sure how to check that.

This is fixed in master, and backported to 5-2-stable in 50036e6.