I've read through the current docs in SVN that discuss the 'sharedKey' attribute, but the docs are very confusing. I'm ready to implement and wanted to double-check my thinking on this.
 
I have a case that exactly mirrors the example given in the HasOne tag documentation in SVN: A base User table plus other tables with data specific to various User types (Consultant, for example). The object relationship is that a Consultant is-a User.
 
Reactor doesn't use the "is-a" syntax, but the docs on the HasOne tag indicate that this can be handled using the 'sharedKey' attribute. What is unclear is where that attribute needs to go. In the docs, it is actually placed on the object tag (but this doesn't match the DTD). The HasOne tag is in both the User object definition and the Consultant object definition. I'm guessing, based on the fact that User needs to be saved first when you save a Consultant, that the sharedKey attribute really needs to go on the HasOne tag inside the Consultant object definition, like this:
 
<object name="User">
    <hasOne name="Consultant">
        <relate from="ID" to="userID" />
    </hasOne>
</object>
 
<object name="Consultant">
    <hasOne name="User" sharedKey="true">
        <relate from="userID" to="ID" />
    </hasOne>
</object>
 
Is this the correct way to do it?

Christopher Bradford
Alive!, LLP

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[email protected]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Reply via email to