generator doesen't respect schema of table

ambermoon · **Joined:** Mon Apr 26, 2004 5:17 pm **Posts:** 13

Hi there,

Is it true, that a generator doesen't respects the schema from the class?
for example:

Code:

<hibernate-mapping package="ch.globus.nglr" >
   <class name="NglrHeader" table="NGLR_HEADER"    schema="XXX">
      <id
         column="HEADERID"
         length="10"
         name="headerId"
         type="int"
         unsaved-value="0"
      >
         <generator class="increment" />
   </id>
      <property
         column="COMPANY"
         length="5"
         name="company"
         not-null="true"
         type="int"
       />

The error comes like this: SQL0204N "DB2ADMIN.NGLR_HEADER" is an undefined name.

After changing to:

Code:

<hibernate-mapping package="ch.globus.nglr" >
   <class name="NglrHeader" table="NGLR_HEADER" schema="XXX">
      <id
         column="HEADERID"
         length="10"
         name="headerId"
         type="int"
         unsaved-value="0"
      >
         <generator class="increment" >
         <param name="schema">XXX</param>
         </generator>
      </id>
      <property
         column="COMPANY"
         length="5"
         name="company"
         not-null="true"
         type="int"
       />

It works...

Is this the real case?

emmanuel · **Posted:** Mon May 03, 2004 7:28 pm

This is a known bug and won't be fixed (too uggly).

ambermoon · **Joined:** Mon Apr 26, 2004 5:17 pm **Posts:** 13

Ok...

So what's the best workaround then for this case?

michael · **Posted:** Tue May 04, 2004 4:47 am

Exactly the one you posted already

emmanuel · **Posted:** Tue May 04, 2004 4:56 am

Try a custom generator taking schema as a parameter

ambermoon · **Joined:** Mon Apr 26, 2004 5:17 pm **Posts:** 13

Can i set in this case the schema for the generator at runtime?

Because i get the schemas from an other resource depending of the company i'm working on at runtime.

emmanuel · **Posted:** Wed May 05, 2004 11:57 am

Kind of
By reading the DOM and updating it before sending it to configure(DOM).
Not that elegent however

JustKeith · **Joined:** Thu Jan 22, 2004 8:22 pm **Posts:** 48

I ran into the same difficulty using DB2 sequences and also have the problem that the schema can be differant in differant environments. My solution was a hacked version of the DB2Dialect class. It's not a perfect solution. After using it for awhile I discovered it work somewhat by happenstance but in our environment it does work. It doesn't use the schema from the table but from the hibernate configuration. If you'd like I can send you a patch against the 2.1 for this. It might also work for your environment.