While designing the user management part of my application, I decided to link my user table and address table by way of a 'user' field in the address table. However, 'user' wasn't the primary key, so this broke things when I tried to call getAddressRecord() on my user object. Was this just a bad design decision on my part, or a limitation of ORM frameworks? I know that Reactor needs the primary key(s) to make the associated records work, and I'm not suggesting there's anything wrong with that, I'm just curious if there is a particular purpose for this limitation. Is there a way to use 'relate from="x" to="y"' on non-primary keys? Or is that something best left up to the gateway to handle?

PS - I've already switched my tables around to work properly, so I'm just asking out of curiosity. :)
-- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/

Reply via email to