Jeremy- Ok, this has taken me way longer than I thought it would, and it's because I think I discovered a problem with either (a) the MockDatabase/spec structure or (b) the way Sequel works when you try to explicitly set a primary key.
I checked in the changes I was working on. The actual code changes to Sequel are literally 2 lines. But I added some more tests to associations_spec because I couldn't get the tests working, and found some failures with the primary key being nil in existing tests. These were masked by the tests checking two dynamic values, which were both nil: http://github.com/nateware/sequel/commit/cbed813772fdf82b434e880368c4094f943b5c3b Just run spec spec/models/associations_spec.rb To reproduce. These don't appear to fail when you're using a primary key that auto- increments. On my local mysql db it appears both the existing API and the new patch I added work as expected. -Nate --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-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/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
