fkcolumn should specify the name of the foreign key column, not the name of the primary key on the other table. In most cases this attribute shouldn't need to be specified at all, Hibernate will create a column for the foreign key automatically. So either the docs are just badly worded, or they deliberately named the keys differently to try and highlight the difference (as opposed to having both primary keys be named "id").
On Tue, Sep 22, 2009 at 10:12 AM, Jeff Chastain <[email protected]> wrote: > > I am looking at the one-to-one relationship, unique foreign key mapping > example in the ColdFusion 9 ORM documentation .. > > > > > > http://help.adobe.com/en_US/ColdFusion/9.0/Developing/WS5FFD2854-7F18-43ea-B > 383-161E007CE0D1.html#WS606584AD-43B2-48c1-B9E6-69A670694BBB<http://help.adobe.com/en_US/ColdFusion/9.0/Developing/WS5FFD2854-7F18-43ea-B%0A383-161E007CE0D1.html#WS606584AD-43B2-48c1-B9E6-69A670694BBB> > > > > . and I am wondering why the Empolyee.cfc has the primary key defined as > EmployeeID whereas the OfficeCubicle.cfc has the primary key defined as id? > In most of the other examples, the primary key is just named 'id', so is > there something special here that requires the Employee object to have the > PK as EmployeeID instead? > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:326496 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
