Comments on: Grails build-test-data plugin version 0.2.3 released

By: tednaleid

tednaleid — Thu, 01 Oct 2009 02:51:35 +0000

@Lucas, it’s aware of the unique constraint, and it would be possible to program it to fill in a value for it. I just haven’t done it mostly because I don’t use more than a couple of unique constraints in my applications (username, a few others) and just sticking a generator closure in the TestDataConfig.groovy is pretty easy and is more flexible (see the section on the wiki about “Generating Dynamic Values”).

If there’s enough demand for attempting to do this automatically, I can look further at implementing it. If the TestDataConfig.groovy doesn’t meet your needs, feel free to raise an enhancement issue (or even submit a patch :).

By: Lucas

Lucas — Wed, 30 Sep 2009 22:34:01 +0000

Why the grails build-test-data plugin isn’t aware of the unique constraint?

By: tednaleid

tednaleid — Wed, 26 Aug 2009 14:00:08 +0000

Thanks for the tip about zipOnly. I missed that previously and that’ll be a big help to not have to do the double bookkeeping of mercurial then actually screwing around with SVN just to release the plugin.

I’m glad you guys are getting use out of build-test-data, thanks again for the patch.

By: Rob Fletcher

Rob Fletcher — Wed, 26 Aug 2009 05:32:27 +0000

WRT The SVN issue: In Grails 1.2-SNAPSHOT the release-plugin command accepts a -zipOnly flag that will only upload the plugin zip file to plugins.grails.org leaving you free to host the code elsewhere (bitbucket, github, etc). That might save you some pain.

Thanks again for a fantastic plugin. With this patch applied we can build useful instances of almost all our domain objects with a parameterless build() call which should prove a huge productivity gain when writing integration tests and fixtures for selenium.