StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POGrails Fixtures + Build-Test-Data tries to create duplicate IDs for objects
primarykey
Id
16928500
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-04T22:22:34.420
FavoriteCount
0
LastActivityDate
2013-06-05T15:15:27.950
LastEditDate
2013-06-05T15:15:27.950
LastEditorUserId
2226039
OwnerUserId
2226039
ParentId
0
PostTypeId
1
Score
0
ViewCount
339
LastEditorDisplayName
text
Body
I'm trying to incorporate fixtures and build-test-data into our grails testing, yet even with the simplest example, I get an id collision when trying to build two of the same class with the build-test-data plugin. I can't help but feel like I'm missing something very simple. This works just fine. Assume everything that needs to be imported is imported. <pre><code>class TemporaryFixturesTests extends GroovyTestCase { /* injected */ def fixtureLoader void testFixtureLoadsProperly() { def fixture = fixtureLoader.load { build { testCompany(Company, name: "TestCompany") testBasicUser(User, username: "TestUserBasic", company: testCompany) } } assert fixture.testBasicUser.company.name == "TestCompany" } void setUp() { //TODO } } </code></pre> Yet this one... <pre><code>class TemporaryFixturesTests extends GroovyTestCase { /* injected */ def fixtureLoader void testFixtureLoadsProperly() { def fixture = fixtureLoader.load { build { testCompany(Company, name: "TestCompany") testCompany2(Company, name: "TestCompany2") testBasicUser(User, username: "TestUserBasic", company: testCompany) testBasicUser2(User, username: "TestUserBasic2", company: testCompany2) } } assert fixture.testBasicUser.company.name == "TestCompany" assert fixture.testBasicUser2.company.name == "TestCompany2" } void setUp() { //TODO } } </code></pre> breaks with the error... <pre><code>nested exception is org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session: [<path removed>.Company#0] </code></pre> This leads me to believe that build-test-data is trying to associate id0 to both companies. That stinks. Can anyone tell me why? --Edit-- It seems the tables in question are not set up to have auto-incrementing ids. So when build test data tries to make me an id column, it makes 0s every time as that is an automatically generated integer. osborp provided the solution for this. Build a TestDataConfig with : testDataConfig { <pre><code>sampleData { '<path removed>.Company' { def i = 0 id = {-> i++ } } '<path removed>.User' { def i = 0 id = {-> i++ } } } </code></pre> } 
Tags
<hibernate><grails><fixtures>
Title
Grails Fixtures + Build-Test-Data tries to create duplicate IDs for objects
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USLionheart
UserOwnerUserId
1. USLionheart
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.