RE: [OJB-developers] Vendor neutral DDL scripting Tool

[Chris G. <CGr...@de...>]

We've already got a tool that will generate a torque db-schema.xml from
a Repository.xml and use that to generate your DDL.  :)  I'm in the
process of incorporating the appropriate ant tasks into the OJB
build.xml, and then you won't need to use db-setup.sql ever again. ;)

It has the added advantage that you won't have to re-write your
repository.xml in Torque's format.

Regards,

Chris

> -----Original Message-----
> From: Bram Meijboom [mailto:br...@in...]
> Sent: Wednesday, May 08, 2002 4:48 AM
> To: 'Joa...@tp...';
> obj...@li...
> Subject: RE: [OJB-developers] Vendor neutral DDL scripting Tool
>=20
>=20
> My idea exactly,=20
>=20
> I also have been looking around and came up with zip/zilch in the=20
> open source projects...
> mainly it it takes a sqlgenerator that is database dependant,=20
> takes care of
> vendor types
> and weird (read oracle 8) jdbc drivers/databases(in oracle 8=20
> a "", empty
> string, is a null ??? ).
>=20
>=20
> -----Original Message-----
> From: Joa...@tp... [mailto:Joa...@tp...]
> Sent: Wednesday, May 08, 2002 10:49 AM
> To: obj...@li...
> Subject: [OJB-developers] Vendor neutral DDL scripting Tool
>=20
>=20
> Hy,
>=20
> you all probably know about the problem with different SQL=20
> dialects for=20
> different Databases. The Query part is actually quite ok, but=20
> DDLs just=20
> won't work on more than one Database, when any advanced=20
> feature is used=20
> (and sometimes "advanced features" are things like text that=20
> is longer=20
> than 255 characters). Most of this differences are just=20
> different names=20
> for a data type (example from db-setup.sql: LONGVARBINARY, BLOB,=20
> BLOB(32k), LONGBLOB, IMAGE). What I think would be great is a=20
> tool that=20
> takes ANSI SQL DDL and executes it on different database,=20
> after modifing=20
> the data types to fit the DB vendors idea of the name. While=20
> converting it=20
> could output warnings about changed behaviour (for example MySQL not=20
> handling spaces at the end of CLOBs correctly). I think=20
> writing such a=20
> tool once is less work than modfing db-setup.sql for each=20
> change and it=20
> would be easier to maintain ("Super-DB v36 does support the new=20
> HYPER_GROOVY_BLOB instead of the old PLAIN_BLOB").=20
> Additionally it would=20
> be a great for us, as our product should run on quite some different=20
> databases ;-)
>=20
> I would be willing to write such a tool, but I almost can't=20
> believe that=20
> there is no such thing out there ('though I didn't find it).=20
> Does anybody=20
> know if there are simillar tools somewhere? And if not does=20
> anyone know if=20
> there is a nice overview about the DDL of some databases?=20
> Especially the=20
> ANSI SQL Datatypes?
>=20
> regards
> Joachim Sauer
>=20
> _______________________________________________________________
>=20
> Have big pipes? SourceForge.net is looking for download=20
> mirrors. We supply
> the hardware. You get the recognition. Email Us:=20
> ban...@so...
> _______________________________________________
> Objectbridge-developers mailing list
> Obj...@li...
> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
>=20
> _______________________________________________________________
>=20
> Have big pipes? SourceForge.net is looking for download=20
> mirrors. We supply
> the hardware. You get the recognition. Email Us:=20
> ban...@so...
> _______________________________________________
> Objectbridge-developers mailing list
> Obj...@li...
> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
>=20