01:32 <Frost> namelessjon: it was, and it was not correct.

01:33 <Frost> namelessjon: It was me not having proper constraints on my associations.

09:01 <namelessjon> Frost: I was more referring to the order dependence of the options

17:55 <lnormous> I'm having some trouble writing a custom setter

17:56 <lnormous> I have a property with type PostGISGeometry

17:56 <lnormous> I want to be able to set the latitude and longitude, so I can do object.update(:latitude => x, :longitude => y), so have written latitude= and longitude= methods, which work perfectly when an object is created, and don't seem to work when it's updated

19:15 <lnormous> Here's a gist, if anyone feels they might be able to help: https://gist.github.com/lukenorman/8163094

19:15 <Cinchy> [gist] gist:8163094 (at gist.github.com, lukenorman on 2013-12-28 19:15)

19:16 <lnormous> I suspect it's to do with the model becoming dirty before the update happens - maybe I'm just approaching it the wrong way, and would certainly welcome any input

19:22 <lnormous> dkubb: You've been really helpful with answering my questions in the past, and if you could spare a minute or two I would appreciate it

19:23 <dkubb> lnormous: sure, what's your question? or should I check the backlog?

19:24 <lnormous> Basically, I have a property with type POSTGisGeometry

19:25 <lnormous> I want to be able to set the latitude and longitude, so I can do object.update(:latitude => x, :longitude => y), so have written latitude= and longitude= methods, which work perfectly when an object is created, and don't seem to work when it's updated

19:25 <lnormous> Here's a gist: https://gist.github.com/lukenorman/8163094

19:25 <Cinchy> [gist] gist:8163094 (at gist.github.com, lukenorman on 2013-12-28 19:15)

19:27 <dkubb> lnormous: can you add the PostGISGeometry property type to that gist?

19:29 <lnormous> It's part of dm-postgis

19:29 <dkubb> ahh ok, I hadn't seen it before

19:30 <dkubb> I think the reason why DM is getting mixed up is because you're mutating a value inside an object

19:30 <dkubb> DM only tracks dirtiness of it's own objects, not the ones it refers to

19:30 <dkubb> in order for DM to know the geom value has been changed, you need to update it

19:30 <dkubb> I'll gist an example, one sec

19:31 <dkubb> lnormous: https://gist.github.com/dkubb/8163221

19:31 <Cinchy> [gist] gist:8163221 (at gist.github.com, dkubb on 2013-12-28 19:31)

19:35 <lnormous> Thank you! I've been stuck on this for a couple of hours, trying various different ways - that's a really nice elegant solution

19:38 <dkubb> cool

19:38 <dkubb> it's untested on my end since I don't have dm-postgis, but I figured you could verify it pretty quickly

19:38 <dkubb> the key is that since the value is being overwritten, DM notices that the value has changed

23:33 <lnormous> dkubb: Sorry to bother you again. What's the best way of getting a table name at runtime. doing Class.storage_name works fine in my shell, but throws errors in my application