-
How is this used?
Where do you run this?
Thanks.
2009-11-12 16:41:04 UTC by maxarbos
-
Actually I just learned that the camel case of the constraints in the domain file is not a problem. Most fields with underscores resolve correctly. However, if I have a db field name such as "custom\_1", The application errors out stating that it can't resolve database field "custom1". I'm still researching and trying to reproduce.
2009-09-23 14:10:48 UTC by zebl
-
Sorry, but composite keys are not supported...
2009-09-23 06:21:27 UTC by ekkelenkamp
-
Hi,
This is not a known bug. I'll have a look at it. Might it be possible for you to upload the xml file of your project to the bugtracker?
Rudie.
2009-09-23 06:19:30 UTC by ekkelenkamp
-
[Reposting to escape underscores]
Using GRAG 1.1 for the first time, pretty cool product. However, I noticed that the created domain class removes underscores from my column names, and converts them to camel case, ie: column name "job\_no" becomes "jobNo" in the domain.groovy file. In the GRAG gui, when I click on a column in my Entity, it shows the Name : "jobNo"...
2009-09-22 17:16:21 UTC by zebl
-
Interesting, underscores were also removed from my post above. Must be some conspiracy.
2009-09-22 17:13:06 UTC by zebl
-
Using GRAG 1.1 for the first time, pretty cool product. However, I noticed that the created domain class removes underscores from my column names, and converts them to camel case, ie: column name "job_no" becomes "jobNo" in the domain.groovy file. In the GRAG gui, when I click on a column in my Entity, it shows the Name : "jobNo", and Column name: job_no...
2009-09-22 17:11:47 UTC by zebl
-
Sorry, this is currently not supported...
2009-09-17 08:53:41 UTC by ekkelenkamp
-
Hi,
is there a way to tell GRAG to generate bi-directional relationships by default (rather than marking all as bidirectional relationships by hand)?
I'm trying to generate an application that allows users to browse the database tables, so they should be able to navigate in both directions.
Thanks.
2009-09-17 08:39:30 UTC by robokaso
-
I second that comment - too hard to read.
2009-09-05 18:45:34 UTC by mikemil
