This is odd... I have a few models that after some time just start doing SELECT "my_tablemy_belongs_to_table".* sort of thing. (Almost like it is trying to reference a join table, but missing a _ between the table names.)
In other words, things work for hours, days or weeks then suddenly goes from SELECT "my_table".* to SELECT "my_tablemy_belongs_to_table".* The associated FROM clause also changes to match. Hundreds of exceptions per minute then ensue and all heck breaks loose. ;') I perhaps am running into a namespace issue or something(?)... how does a model get triggered into changing it's associated table name in runtime? Our temp fix it to just restart the service/app but that's obviously not sustainable. We had to do it several times today. Thoughts? ruby 2.5.0p21 (2018-02-18 revision 62472) [x86_64-linux] rails 5.1.6 pg 1.0.0 Thanks! Phil -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/06C283DC-D65C-4F5D-AD30-2D620B48242F%40gmail.com. For more options, visit https://groups.google.com/d/optout.
