Max Rydahl Andersen wrote:
Well, i think we have found that the feature you want is usable - and
as I see it already in there (as you can get the sql string[]).
Your first posting said you were doing something special, and it was
that "special" think I would like to know what was...now I know (you
I appreciate all your responses, but I don't think we're getting very
far.
Well, i think we have found that the feature you want is usable - and
as I see it already in there (as you can get the sql string[]).
Your first posting said you were doing something special, and it was
that "special" th
Max,
I appreciate all your responses, but I don't think we're getting very
far. I started this thread because between 2.0.0 to 2.0.1 to 2.0.2 the
generateSchemaUpdateScript (the key code in SchemaUpdate) is changing
signatures. In 2.0.1 it changed to JdbcDatabaseInfo, and now it's
DatabaseMe
Eh, well the SchemaUpdate code is pretty trivial, if you look at it.
Here are the salient lines (I think this is from the 2.0.1 version...
2.0.0 and 2.0.2 use DatabaseMetadata instead of JdbcDatabaseInfo)
JdbcDatabaseInfo info = new JdbcDatabaseInfo(connection, dialect);
String[] createSQL = cf
Max Rydahl Andersen wrote:
Sorry - i meant SchemaUpdate.
And now you are just saying 3-4 lines, couldn't you just show us what
you are doing and we could add that as a integral part of SchemaUpdate
(and even SchemaExport i reckon).
Eh, well the SchemaUpdate code is pretty trivial, if you look at
Sorry - i meant SchemaUpdate.
And now you are just saying 3-4 lines, couldn't you just show us what
you are doing and we could add that as a integral part of SchemaUpdate
(and even SchemaExport i reckon).
/max
Serge Knystautas wrote:
Max Rydahl Andersen wrote:
So - just using the "dump sql to
Max Rydahl Andersen wrote:
So - just using the "dump sql to the standard output" is not enough for
you ? (You can parse that up to an array by just looking for ";"'s)
No it is not. The key is "standard output" is the killer.
Why should my Java code have to fork a separate process, suppply my
co
Max Rydahl Andersen wrote:
But - why don't you try to explain WHY you need this copy-pasting, maybe
it's a feature that can be integrated into SchemaExport OR it could
provide the motivation for having a more public stabilzied apiso
please, tell use more ,)
I gave a pretty complete descriptio
I guess that the code you are using is part of the internal parts of
SchemaUpdate (as opposed to being part of any public api) - thus I don't
think you will get any guarantees on that being stabalized!
But - why don't you try to explain WHY you need this copy-pasting, maybe
it's a feature that ca
