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
When updating to Rails 4, I've encountered a nasty error message:
ActiveRecord::StatementInvalid:
PG::SyntaxError: ERROR: zero-length delimited identifier at or near """"
LINE 1: ..._table".* FROM "my_table" ORDER BY ""."rgt" d...
^
: SELECT "my_table".* FROM "my_table" ORDER BY ""."rgt" desc LIMIT 1
The model implementing nested_set is quite simple:
The delegation of quoted_table_name to self isn't working anymore (at least with abstract models) and I guess it may be related with this issue rails/rails#10658.
Defining self.quoted_table_named in my abstract model seems to solve the problem, though it feels a little hacky, and may not be the perfect solution for everybody facing this problem.
Not sure if this is an awesome_nested_set issue (I really don't think so) but I think it's important to point that out.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
When updating to Rails 4, I've encountered a nasty error message:
The model implementing nested_set is quite simple:
Everything was fine with Rails 3.2, but when updating to Rails 4, it started to break. After some source digging I've seen this: https://github.com/collectiveidea/awesome_nested_set/blob/master/lib/awesome_nested_set/model.rb#L17
The delegation of
quoted_table_name
toself
isn't working anymore (at least with abstract models) and I guess it may be related with this issue rails/rails#10658.Defining
self.quoted_table_named
in my abstract model seems to solve the problem, though it feels a little hacky, and may not be the perfect solution for everybody facing this problem.Not sure if this is an awesome_nested_set issue (I really don't think so) but I think it's important to point that out.
The text was updated successfully, but these errors were encountered: