ORM Relationships - "Repeated column problem"

Question

Hi there
I'm having a problem with relationships in ORM. I have set up one that is working but another is not.
I am getting the error;
Repeated column in mapping for entity: company column: company_id (should be mapped with insert="false" update="false")
I have 3 components; company, country and city.
<!--- ORM companies --->
<cfcomponent persistent="true" table="companies">
<cfproperty name="company_id" fieldtype="id" generator="native">
<cfproperty name="company_name">
<cfproperty name="address1">
<cfproperty name="address2">
<cfproperty name="address3">
<cfproperty name="city_id">
<cfproperty name="postcode">
<cfproperty name="web">
<cfproperty name="telephone">
<cfproperty name="fax">
<cfproperty name="company_description">
<cfproperty name="date_added">
<cfproperty name="added_by">
<cfproperty name="date_last_updated">
<cfproperty name="last_updated_by">
<!--- Create Relationship to city.cfc :: Not working?????? --->
<cfproperty name="City" fieldtype="one-to-one" cfc="city" fkcolumn="company_id" inverse="true">
</cfcomponent>
<!--- ORM country component --->
<cfcomponent persistent="true" table="countries">
<cfproperty name="country_id" fieldtype="id" generator="native">
<cfproperty name="country_name">
<cfproperty name="currency_id">
<cfproperty name="flag">
<!--- Create Relationship to city :: This works fine --->
<cfproperty name="Cities" fieldtype="one-to-many" cfc="city" fkcolumn="country_id" inverse="true">
</cfcomponent>
<!--- ORM City --->
<cfcomponent persistent="true" table="cities">
<cfproperty name="city_id" fieldtype="id" generator="native">
<cfproperty name="country_id">
<cfproperty name="city_name">
<!--- Create "many-to-one" Relationship back to country :: Also Doesn't work for some reason?? --->
<cfproperty name="Country" fieldtype="many-to-one" cfc="country" fkcolumn="country_id">
</cfcomponent>
This works fine;
<cfset cnt = EntityLoad("country")>
<cfdump var="#cnt#">
I can see my cities when I dump out the countries
Can someone tell me why my other relationships in particular the first one are failing??
Thanks folks
Ian.

Answer 1

theraptor wrote:
I probably didn't explain it correctly. I am trying to populate these tables with data about financial instruments.
Table 2 and 3 share a primary key (INSTRUMENT). The primary key is generated in table 2, and the same value has to be later inserted into table 3. Sorry, I'm not following this at all. I don't think two tables should "share" a primary key. Both should have their own. Perhaps Table 3 would have a foreign key relationship with Table 2. OR the two tables should be one. But this notion of sharing doesn't sound right to me, and apparently Hibernate agrees. I think you have a bad design.
Table 2 has a one to many relation with table 3. Then they can't share a primary key. It's 1:m, which you can easily model with Hibernate.
(By many I mean it could be 0 as well, since hibernate does not provide a (one to 'maybe' one 'maybe zero) relation.Fine. Then it's a 1:m relationship. You've been thinking about it incorrect.
Table 3 has an additional column PARENT_INSTRUMENT which is a foreign key to the the primary key of table 2.No. Wrong.
Yes Instrument is financial in nature. However, I am not trying to model what you have spoken about above.Yes, I get it. Listen to Hibernate - your original idea is quite incorrect. Table 2 is 1:m with Table 3. Model it that way, and forget about this incorrect notion of "sharing a primary key". Give Table 3 its own auto generated key.
%