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
Thanks, I'm just looking at this. Could you provide MergerTokenComparator
as well or describe what it does?
John
On Fri, Oct 7, 2011 at 6:19 PM, Dave Lamy wrote:
> Sure, here's a snippet. This iterates through all nodes/maps in a
> DataDomain and executes the merge. Note that it has logic to
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
