On Aug 26, 2008, at 22:39, Scott Anderson wrote:
Moving this to the list, since it maybe useful to others-
I have been poking around, and I think I've figured out how to use it.
If I use DbGenerator, everything works great, but if I try to merge in
changes from a slightly out of sync schema wit
L PROTECTED]
Sent: Tuesday, August 26, 2008 2:30 PM
To: Scott Anderson
Subject: Re: DbGenerator vs. MergeContext
On Aug 26, 2008, at 19:25, Scott Anderson wrote:
> Are there any examples of how to do this in code? It would be nice to
> have Cayenne do all the heavy lifting here, since the idea o
On Aug 22, 2008, at 3:07 PM, Tore Halset wrote:
On Aug 22, 2008, at 13:36, Andrus Adamchik wrote:
Interesting... I am not using either for anything complex lately,
preferring manual SQL scripts executed with dbpatch Ant task, so I
am a bit out of the loop.
The sql-scripts is a very solid
A little bit of a non-sequitor here... but I'm wondering whether it is
correct to fix
the issues below in the Merge stuff.
1. I'm wondering where the responsibility lies for making sure that the
entry of an AUTO_PK_SUPPORT is > max of pk. A table may exist before
AUTO_PK_SUPPORT is added.
59563 [
On Aug 22, 2008, at 13:36, Andrus Adamchik wrote:
Interesting... I am not using either for anything complex lately,
preferring manual SQL scripts executed with dbpatch Ant task, so I
am a bit out of the loop.
The sql-scripts is a very solid way to work, but some people would
probably pref
Interesting... I am not using either for anything complex lately,
preferring manual SQL scripts executed with dbpatch Ant task, so I am
a bit out of the loop.
So Tore, would you consider the merge package a logical superset of
DbGenerator (even though not all features are there yet)? Or is
Hello.
There are still some things missing from the merge-package to be able
to create a complete database from scratch. Like the ability to
correctly order the tables that are to be created. However, I use
merging a lot more than generating.
Regards,
- Tore.
On Aug 22, 2008, at 10:53,
Is the DbGenerator an anachronism as far as applications are concerned
at this point?
E.g. I discovered that the AUTO_PK_SUPPORT is correctly added w/MergeContext
whereas DbGenerator resets the counters to 200.
Perhaps the JavaDoc for DbGenerator should encourage use of MergeContext?
--
Øyvind