[Deprecated] DMZ 1.5.3 (DataMapper OverZealous Edition)

[eluser]ntheorist[/eluser]
hrm, what i mean with extending tables automating the joining of the extending model to the base model without having to specify relationships.

So say the person table would have the columns

id, firstname, lastname, phone, email

and a User

id, person_id, username, password, lastlogin, salt, (inherits firstname, lastname, phone, email from person)

This wouldn't be meant to be a standard 'parent' relationship. whenever you call a new User(), it would automatically join the users table to the people table, and act as if they were one. Users would have extra fields but would always inherit from the people table, as well as its methods and such, sort of reflecting OO extends, methods, overrides etc. There'd be some tricky things with this, how to merge validation for instance, or inherit relationships.. but does it make sense? You could take it further and have a table 'admins' which extends users which extends people, and admin inherits or overides fields/relationships from each of them in turn.

I may try adopting this into DMZ possibly using include_relations within the constructor but i don't want to hack your library up too much. The other thing is i've also invested a lot of time upgrading the original to do what i wanted and now my prob is I have a working version I like, and do i ditch it and go with DMZ or try to integrate it with the functionality you've developed? I thought it would be neat to release it as a Datamapper fork but i dunno if people need another DM library (plus i don't want to step on DMZ's toes ) Also if i were going to do that i'd have to write up my own docs and such and it IS a tremendous effort, i definitely give you props for your work there its really helpful.

anyway i'll continue thru the weekend checking out code and testing integration. I'll be awaiting the next release too, it seems like its making good progress and I like the features you're adding to it.

thx,

n