Changing the column name from firstPeer to first_peer helped. Apparently postgre, as you pointed out, couldn't handle the camel case but automatically lower cased it. This was not any fault of AR's. On the contrary, in the code where I let AR create the SELECT, the field name was handled correctly, in a way that postgresql could understand.
Thanks Fred! 2009/2/22 Frederick Cheung <[email protected]> > > > > On Feb 22, 8:39 pm, Felixyz <[email protected]> wrote: > > I'm trying to deploy a Rails app on a platform using Thin, after some > > horrible sessions trying to make it work with fcgi. All is going well, > > but my Application controller throws this error: > > > > ActiveRecord::StatementInvalid (PGError: ERROR: column "firstpeer" > > does not exist > > LINE 1: SELECT * FROM "switches" WHERE (firstPeer = 15 OR > > secondPeer... > > Well I don't know pg much, but > http://www.postgresql.org/docs/8.0/static/sql-syntax.html > says that unquoted names are folded to lowercase. > > Fred > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
