StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17593854
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-11T12:50:17.430
FavoriteCount
0
LastActivityDate
2013-07-11T12:50:17.430
LastEditDate
LastEditorUserId
0
OwnerUserId
1833961
ParentId
11299675
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<p>I had the same problem. I am not sure if the root-cause is the same. But there turned to be a perfectly logical explanation. So here is what I discovered.</p> <p>First of all, there are at least 2 distinct ways to create auto-incremented keys.</p> <h2><strong>1st way: (xml)</strong></h2> <p>If you work with an xml-based configuration that holds your class info. Then you can put something as follows in your classname.hbm.xml file.</p> <pre><code><id name="id"> <generator class="sequence"><param name="sequence">my_id_seq</param</generator> </id> </code></pre> <p>To import this file you will have something like the following in your hibernate.cfg.xml file: (or possibly with a resource attribute)</p> <pre><code> <mapping file="classname.hbm.xml"/> </code></pre> <p>But the important thing here is that it is now actually JAVA that will increment the keys. If you would have checked the sql that was used to generate the table, you would have noticed that it did not hold an auto-incremented field definition for the id column.</p> <h2><strong>2nd way: (annotations)</strong></h2> <p>A totally different way of doing things is to put everything in annotations, like you showed in your question.</p> <pre><code>@GeneratedValue(strategy=GenerationType.IDENTITY) </code></pre> <p>in your hibernate.cfg.xml file you will have something like:</p> <pre><code> <mapping class="package.subpackage.MyClassName"/> </code></pre> <p>The GenerationType.IDENTITY is indeed the default value, so you do not have to supply it per se. But anyway this time the table will be generated differently. Namely as follows:</p> <pre><code>CREATE CACHED TABLE PUBLIC.MYTABLENAME( ID INTEGER DEFAULT (NEXT VALUE FOR PUBLIC.SYSTEM_SEQUENCE_9DE2A0D5_28F5_488F_9E4C_2878B3CDA72F) NOT NULL NULL_TO_DEFAULT SEQUENCE PUBLIC.SYSTEM_SEQUENCE_9DE2A0D5_28F5_488F_9E4C_2878B3CDA72F, ... ) </code></pre> <p>Aha! That's interesting. This time the sequence generation will not be performed by JAVA it will be performed by the database itself.</p> <h2><strong>What went wrong:</strong></h2> <p>We are all experimenting and trying things out of course. If you first decided to do it with the xml-files and afterwards you decided to do it with annotations after all. Then of course that means you will have to regenerate your tables as well. If you forget to do so, then you will get errors like doniyor did.</p> <h2><strong>How to fix it:</strong></h2> <p>just add the following line to your hibernate.cfg.xml and reboot your application.</p> <pre><code> <property name="hibernate.hbm2ddl.auto">create</property> </code></pre> <p>The table has been destroyed and regenerated.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POhow to set H2 primary key id to auto_increment?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USbvdb
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.