I have a program which runs fine under Hibernate 2 with a table which uses a date as the primary key. The mapping looks like this:


Hibernate will now complain when inserting new records that it "cannot perform lookups on timestamps". In this instance we are using MySQL 4.1.7-nt. Is this changed behavior? Should we be doing this another way?

Thank you

Tom

It is very dangerous to use a timestamp as a primary key. Why would you do this?

I changed it to a java.util.Calendar field actually and it works fine.

In this particular application we recieve a data feed once per day. We didn't need a time stamp per say but we definately wanted to associate a batch of data with a particular time / date which it was generated. Having two files with an identical date / time would not be possible.

Thanks

Tom

If something is a time indexed sequence come to think of it, why would having a date / time object be a bad idea as an index?