> what could be stopping a valid, dirty model from being saved? There is a known bug if you retrieve an object through a belongs_to relation that saving the object won't work.
Example: address = Address.get(1) person = address.person person.name = "Whatever" person.save # This will report true, but it didn't actually save We're in the middle of a spec rewrite, so we don't want to touch the code too much. The whole save behavior needs to be properly defined, so when these specs are done, these bugs will all be fixed. I don't really dare now to touch that code too much, because I have no idea what will break. These kind of resources also fail now with Merb's resource() method, because they are actually proxy objects and not real resource objects. -- Regards, Dirkjan Bussink --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
