Closed rurabe closed 10 years ago
Note that rows
seems to be the only thing that sets this off, when I do sections
as an association it works fine. I think rows is a keyword in postgres. But quoting the string allows for columns of any name.
I went to create a test for this and it passes, was this fixed by 7c06bee3cd4a34158db458d3cdd2ad2d4aa3f724 ? Is that why I can't find where the probem is haha?
If so, any plans on releasing soon? Or should I point to github?
Yes, it looks like it was fixed by 7c06bee. But it did reveal a potential issue in the code path where association names should be quoted. So I made that change and added a test.
I've released a new version to rubygems.com.
I have a model named Row, which seems to be giving me errors.
which results in:
which gives:
If I manually edit the sql to put quotes around
"rows"
:then it works as expected.
I'm not very familiar with how AR works under the hood, so I poked around in the code but couldn't find where this is getting generated. Is this a surus issue? Or is it in AR?