Autonaming of foreign key constraints

quereinsteiger · **Joined:** Sat Oct 11, 2003 11:13 am **Posts:** 69

When I execute the schemaexport, the generated DDL script contains cryptic foreign key constraint names like:

Quote:

alter table Address add index (PERSON_ID), add constraint FK1ED033D4D8F32245 foreign key (PERSON_ID) references Person (PERSON_ID);

The name FK1ED033D4D8F32245 starts good (FK), but ends bad (1ED033D4D8F32245).

Is there a feature with autonaming? I mean it would be good if the schemaexport could name the foreign key constraints automatically to FK_PERSON.

I tried to do it manually. It does not seem to work with Hibernate XDoclet tags:

Code:

   /**
     * @hibernate.set
     *  cascade="all"
     * @hibernate.collection-key
     *  column="PERSON_ID"
     * @hibernate.collection-one-to-many
     *  class="org.liberty.domainobjects.Address"
     *  foreign-key="FK_ADDRESS"
    * @return java.util.Set
    */
   public Set getAdresses() {
      return adresses;
   }

It had no effect on the generated hbm.xml file.[/code]

emmanuel · **Posted:** Tue Feb 24, 2004 5:37 pm

Add this feature to Jira.

quereinsteiger · **Joined:** Sat Oct 11, 2003 11:13 am **Posts:** 69

emmanuel wrote:

Add this feature to Jira.

I did it. HB-742

Jira makes a much better impression than the tracking tool which we have to use in our company (a product called "Magic")!

emmanuel · **Posted:** Wed Feb 25, 2004 6:47 am

I prefer Bugzilla for it's search capabilities, but JIRA for everything else.