On Wed, Jan 28, 2009 at 6:35 PM, Frederick Cheung <[email protected]> wrote: > Hmm. The problem you have is that by setting primary key > to :table_name_with_underscore rails wants to use session_id as the > primary key to the sessions table. it also wants to use session_id for > the session identifier and for whatever reason, the primary key 'wins'. > You could fiddle the SessionClass for it to store the session > identifier in a different column (or > CGI::Session::ActiveRecordStore::Session.set_primary_key 'id' would > probably do the trick if you can get away with it.
I appreciate the reply but I'm not gonna bother trying to figure it out, I switched to memory sessions this morning and it works with no problems. I'm not really understanding how I can have another app on Rails 2.0.2 that has this exact same setup and it works fine. Something changed from 2.0.2 -> 2.2.2 which obviously didn't break any Rails core tests.. I mean, if anyone is even testing on anything besides MySQL. To use Rails in medical research means Oracle most of the time. -- Greg Donald http://destiney.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
