On Wed, Oct 12, 2011 at 4:13 AM, Durchholz, Joachim
wrote:
> Maintaining a set of scripts so that it remains consistent with the database
> would be just a waste of effort. It is unlikely that they'd ever need such
> scripts anyway: the ability to create an empty database would be worthless to
John Huss wrote:
> I'd say it not essential.
If a N:1 relationship is based on a UK that's not known to Cayenne, Cayenne
will be forced to assume an N:M relationship.
This means that on the N side, the Java object will have a Set instead of a
simple reference.
I'd consider stuff that affects th
But I'd say it not essential. In any project of decent size you're likely
to have SOME additional sql to execute to set up your database, be it
creating views or functions or triggers or indexes. It's definitely not the
modeler's job to handle all that stuff. So if you have to execute custom
My 2 cents: Coming from the WebObjects world, their modeler does let you
define indexes (unique or not) in the modeler, and it will generate the sql
for them. It's nice.
But I'd say it not essential. In any project of decent size you're likely
to have SOME additional sql to execute to set up yo
I second this because as i see the DB Modeler is like an abstraction
layer/tool of the database in terms of a model and i would love to skip
any direct contact with the database (as i don't really care about the
specific database backend itself as long as it adheres and fulfils
Cayenne requirem
I think the biggest argument for keeping constraints in the model is
that it could be used in the future to help Cayenne determine better
orders of operation.
mrg
On Mon, Oct 10, 2011 at 10:11 PM, Aristedes Maniatis wrote:
> On Mon Oct 10 20:32:13 2011, Durchholz, Joachim wrote:
>>
>> Just givi
On Mon Oct 10 20:32:13 2011, Durchholz, Joachim wrote:
Just giving feedback from my user perspective:
CayenneModeler is not a DB admin tool, so DB concepts not directly related to
ORM are generally ignored.
I find that reasonable.
UNIQUE indexes are somewhat on the border and I even believ
Just giving feedback from my user perspective:
> CayenneModeler is not a DB admin tool, so DB concepts not directly related to
> ORM are generally ignored.
I find that reasonable.
> UNIQUE indexes are somewhat on the border and I even believe we have a
> feature request in Jira somewhere...
T
On Oct 8, 2011, at 12:17 AM, Daniel Scheibe wrote:
> i was just asking myself if i'm missing something or if its not possible to
> configure unique index constraints inside cayenne modeler?
You are correct. CayenneModeler is not a DB admin tool, so DB concepts not
directly related to ORM are g
