On Monday, July 7, 2014 4:23:51 PM UTC-7, Chris Fincher wrote: > > Hi Everyone (but mostly Jeremy from the looks of things?), > > I've been working on upgrading the version of Sequel our app uses, and > I've come across a bug I'm having trouble breaking apart. Here's the error > I get: > > E, [2014-05-12T15:58:09.183705 #88865] ERROR -- : mismatched number of > composite keys: [:deal_id] vs [] (Sequel::Error) >
This indicates that it doesn't know what the primary key for Deal is. What does Deal.primary_key give you? You can force a primary key for Deal using set_primary_key :id. Looking at the changes in the oracle adapter between 3.34.1 and 3.35.0, the only thing related to schema parsing in the oracle adapter is a change from using dba_tab_cols to user_tab_cols. That was done so that parsing column default values works as a non-superuser. I don't know enough about Oracle to determine if that has other effects, but it doesn't sound like it should. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
