Hibernate主键生成策略

increment
generates identifiers of type long, short or int that are unique only when
no other process is inserting data into the same table. Do not use in a
cluster.
identity
supports identity columns in DB2, MySQL, MS SQL Server, Sybase and
HypersonicSQL. The returned identifier is of type long, short or int.
sequence
uses a sequence in DB2, PostgreSQL, Oracle, SAP DB, McKoi or a
generator in Interbase. The returned identifier is of type long, short or int
hilo
uses a hi/lo algorithm to efficiently generate identifiers of type long,
short or int, given a table and column (by default hibernate_unique_key

and next_hi respectively) as a source of hi values. The hi/lo algorithm
generates identifiers that are unique only for a particular database.
seqhilo
uses a hi/lo algorithm to efficiently generate identifiers of type long, short
or int, given a named database sequence.
uuid
uses a 128-bit UUID algorithm to generate identifiers of type string,
unique within a network (the IP address is used). The UUID is encoded
as a string of hexadecimal digits of length 32.
guid
uses a database-generated GUID string on MS SQL Server and MySQL.
native
picks identity, sequence or hilo depending upon the capabilities of the
underlying database.
assigned
lets the application to assign an identifier to the object before save() is
called. This is the default strategy if no <generator> element is specified.
select
retrieves a primary key assigned by a database trigger by selecting the
row by some unique key and retrieving the primary key value.
foreign
uses the identifier of another associated object. Usually used in
conjunction with a <one-to-one> primary key association.
sequence-identity
a specialized sequence generation strategy which utilizes a database
sequence for the actual value generation, but combines this with JDBC3
getGeneratedKeys to actually return the generated identifier value as
part of the insert statement execution. This strategy is only known to be
supported on Oracle 10g drivers targetted for JDK 1.4. Note comments
on these insert statements are disabled due to a bug in the Oracle
drivers.