Hi I'm trying to save a transient object, with session.saveOrUpdate(object), however when the statement executes the primary id is included in the query and is given a null value.

Is there anyway to insert without the primary key??

I am using xDoclet to tag the object class, and using the generator class
'identity' to generate keys.


Thanks


Hibernate version:3.1

Full stack trace of any exception that occurs:
10:46:05,546 WARN JDBCExceptionReporter:71 - SQL Error: 339, SQLState: S1000

10:46:05,546 ERROR JDBCExceptionReporter:72 - DEFAULT or NULL are not allowed as explicit identity values.

10:46:05,562 ERROR HibernateCustomerService:? - org.hibernate.exception.GenericJDBCException: could not insert: [domain.WebAccessCode]

Name and version of the database you are using:
MS SQL 2005

The generated SQL (show_sql=true):
Hibernate: insert into dbo.CustWebAccess (cwa_AccessCode, cwa_custnum, cwa_nopricetext, cwa_password, cwa_permitacct, cwa_per
mitadmin, cwa_permitbackorder, cwa_permiteditusers, cwa_permitorder, cwa_permitseecost, cwa_permitseesell, cwa_permitupload,
RecID) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, null)

in the mapping file, define where the primary key is supposed to come from.

something like


and/or, set the unsaved-value attribute to null so hibernate knows that it is a new row and it's not supposed to actually set the pk to null.

Hi,

I added the unsaved-value="null", but I'm still getting the same error, I've also tried the 'native' generator with no success.

it's still trying to insert RecID with the query with the value null.

Thanks

Here's part of the .hbm.xml file that's generated:

<id
name="recId"
column="recID"
type="java.lang.Integer"
unsaved-value="null"
>
<generator class="identity">
<!--
To add non XDoclet generator parameters, create a file named
hibernate-generator-params-WebAccessCode.xml
containing the additional parameters and place it in your merge dir.
-->
</generator>
</id>

Where is the pk supposed to come from for your row?

Since I'm making a session.saveOrUpdate(Object) call,

I thought that it's supposed to get auto-generated by the database, as according to the id generator-class, which in this case I have set to identity.

No where in my application do I actually set the PK, I'm under the assumption that Hibernate and the database handles all of that.

So currently I'm creating the object, using:

new WebAccessCode(),

setting all it's properties except the PK, and sending it to the query.

Am I missing something?

thanks

Hi,

are you sure your database supports autoincrement? which database are you using.

-Praful

Hi,

I'm using MS SQL server 2005,

I've run a manual insert through a sql browser

without specifying the primary key and it works fine, so I'm pretty sure it'll auto-increment.

Could the problem be related to my database driver? I'm using

jtds-1.2.jar for my driver.

Thanks

try


this will tell hibernate that the database is going to generate the primary key

Yup

tried the 'native' generator class as well, didn't work.

how are you trying to save it? Is it a new object?

Most of my entity tables in Sql Server 2005 database relay on identity columns to autogenerate the primary key.

I used "native" and "identity" generators, as well as proposed solutions above.

The things is how to tell hibernate to not to pass the NULL value to the underlaying driver when inserting.

In this sample table:

[User]
Id int (identity) PK
Name varchar
Age int

For example, it should generate the following SQL:

insert into [User] (Name, Age) values ('jvargas', 24);

instead of this one:

insert into [User] (Id, Name, Age) values (NULL, 'jvargas', 24);

Because Sql Server 2005 do not allow to pass NULL or DEFAULT values when inserting on Identity columns, the columns should not be specified at all when inserting.

So, how to ignore the PK column in the generated insert ?

jvargas,
Do the following to get up and running:


Using Enterprise Manager remove the identity insert property from your table.

Apply a primary key to this column (if you haven't already).

Then set your key generation to increment.

EX:



I've found it's better to allow hibernate to handle the key generation in lieu of sql server.

Hope that helps.


Philip