Hi all,
Say, I have a table CAT with a primary key CAT_ID.

I need to auto generate CAT_ID using:
<generator class="native"/> OR <generator class="identity"/>

But if I have a value for CAT_ID in the object, I don't want a generated id.

I am using session.save(newCat) to persist the object 'newCat'.

How do I go about doing this?

Thanks a lot.
Cheers

You may only specify one generator.

If you already have a identifier in an object you shouldn't be saving it - you should be updating it.

but...

I'm not sure if i understand your question. If you have a value for catId in the object does it already exist in the database?

Hi drj,
This is actually for 2 different environments. Both environments will have seperate copies of code and database.

In one environment 'Development', all objects will be inserted with the generated IDs.

Now, when I am inserting selected data from 'Development' to another environment 'Test', they should carry the same IDs as in 'Development'.

Thanks

If they are separate environments then I assume they will have separate hbm.xml files.
You could use the generated identity in one environment (dev) and the other generator in the non-development environment but you would need to be aware of the implications of this.

I'm beginning to question the use of hibernate in this situation. Is this is bulk transfer of data?

Hi drj,
The same version of code needs to reside on both the environments.

Is it possible to determine during runtime what *.hbm.xml file will be used? Say, have something like CatDevelopment.hbm.xml and CatTest.hbm.xml ? I can determine what environment I am in by a Java environment varaible. Will this help in deciding what *.hbm.xml file to use?

We are not performing bulk transfer. We have used hibernate in other modules of the project; so just maintaining consistency.

I have set up the tables in such a way that it will auto-generate id's if not present. For this I have used the GENERATE BY DEFAULT IDENTITY feature in DB2. Since DB2 does it, I was wondering why not Hibernate?

Thanks

The solution is the Session.replicate() method in Hibernate 3.0

Here's a snippet from the Hibernate Reference Manual (10.9):