• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

hibernate primary key mapping - sequence

 
Eugene Babiev
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
in the following xml the sequence is defined (for Oracle DB):

<id name="id" column="PENDING_ORDER_ID"
unsaved-value="-1">
<generator class="native">
<param name="sequence">
UNIQUE_ID_SEQUENCE</param>
</generator>
</id>

but what if the alternative database is MySQL which doesn't have sequences. Then what the hibernate will do in this case? Should i write another MySQL mapping to exclude sequence param from mapping?

regards,
Eugene
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can't use sequences with MySQL, so I presume Hibernate will throw some sort of exception if you try. The sequence generation strategy will only work with those DBs that support sequences (DB2, PostgreSQL, Oracle, SAP, McKoi and Firebird). Its a little gotcha in Hibernate's "one mapping layer for all databases" claim, albeit an understandable and documented one.

However that mapping you posted is a native generation strategy, not a sequence generation stategy. Native will use another generator depending on the database. If its Oracle for example Hibernate will look for a sequence called UNIQUE_ID_SEQUENCE. If its MySQL, it will try to use something else (probably identity - but you'll find that out when you run it against your MySQL schema).
 
Jeff Albertson
Ranch Hand
Posts: 1780
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why not try it and see what happens?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic