[Hibernate-issues] [Hibernate-JIRA] Commented: (HBX-622) Allow ability to ignore Foreign Keys

[George L. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-622?page=comments#action_22583 ] 

George Lindholm commented on HBX-622:
-------------------------------------

I also need something like this, except that I need 
to be able to exclude specific columns in one table
that refer to a second table.

Eg: I have

<hibernate-mapping>
    <class name="ca.ubc.nmc.contacts.db.NcContact" table="NC_CONTACT">
        <id name="contactId" type="long">
            <column name="CONTACT_ID" precision="10" scale="0" />
            <generator class="ca.ubc.nmc.contacts.ContactIdGenerator"></generator>
        </id>
        <timestamp name="lastUpdtDate" column="LAST_UPDT_DATE" />
        <many-to-one name="role" class="ca.ubc.nmc.contacts.db.NcRoleTypeTbl" fetch="select">
            <column name="ROLE" length="4" />
        </many-to-one>
        <many-to-one name="orgUnitIdAndorgUnitType" class="ca.ubc.nmc.contacts.db.NcOrgUnit" fetch="select">
            <column name="ORG_UNIT_ID" length="10" />
            <column name="ORG_UNIT_TYPE" length="4" />
        </many-to-one>

and I want to programatically have ORG_UNIT_ID and ORG_UNIT_TYPE mapped to
normal String values, instead of keys to another table.


> Allow ability to ignore Foreign Keys
> ------------------------------------
>
>          Key: HBX-622
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-622
>      Project: Hibernate Tools
>         Type: New Feature

>   Components: reverse-engineer
>     Versions: 3.1beta4
>  Environment: As per patch.
>     Reporter: James Olsen
>  Attachments: svn-patch.txt
>
>
> On the project I'm currently working on we want 1:1 POJO<->Table mapping without any relationships between the POJOs.  Although this is not a configuration that I would normally choose or recommend, in this case it is forced upon us be external architectural requirements.
> Currently in order to avoid relationships in your POJOs you have to reveng each table individually.  The attached patch is a proposed solution to allow the reveng to ignore relationships between tables when reverse engineering multiple tables at the same time.
> Note that the patch only supports this for ReverseEngineeringStrategy not for reveng.xml.
> I'm supplying the patch in the hope that it (or something similar) can be incorporated into the main code and in case anyone else has (unfortunately) similar requirements.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira