This was a problem with included Modules also providing attr_accessors for the properties, i.e., a module has
attr_accessor :foobar And an including model has property :foobar Up to at least rc2, this actually worked. And so I just didn't notice the old attr_accessors still hanging around. And with 1.0.0, it doesn't —which seems fair. Pure coincidence that all the "duplicated" properties also happened to be BigD (modules bring in common WGS84 and currency handling to a lot of models.) Hopefully no one else has that dumb an oversight, but if so, hope this helps. On Jun 10, 11:49 pm, Yuri <[email protected]> wrote: > What I'm seeing: in the 0.10 series and up to rc2 (I skipped rc3 > because of the change to belongs_to), properties declared BigDecimal > saved if given in a string or a BigDecimal. As of 1.0.0, an object > with a property declared BigDecimal (or plain Decimal) given a string > for that property will silently fail to save. If given a BigDecimal > the value will be applied, and be retrievable by the getter after > create, but will not appear in the INSERT statement or an instance > loaded, i.e, BigDecimal attrs are not sent to the DB regardless of the > instance's attr value. > > Since I somewhat doubt that situation would have made it past the > tests if it where a DM Core problem, I'm wondering if those symptoms > light a bulb in anyone's head about anything that could be interfering > with DM saving BigD? -- 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.
