2009/10/23 Jeremy Evans <[email protected]>: > I actually work around this Sequel behavior in the application I'm > currently working on, and it got me thinking about whether Sequel's > current behavior is best.
I'm sorry about the 2nd post but it's really bugging me. I cannot figure out how it would ever happen in code where I have the combination of events you describe. Why would you ever try request albums for an artist that's new and not yet saved? I've created many many sites and applications now using Sequel and I can't see how this scenario would ever even happen. Surely at the time of creation you're aware that you're creating a new object so you don't attempt to read from it while it's still being set up prior to the first save. Thanks, Clive --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
