Hi Steve,
Lihn, Steve wrote:
Ludovic,
Thanks for the Mysql port. Can you specify your MySQL environment? Like
version, etc.
I would hope you can use MySQL 5.0 and above where many new features are
available.
I use MySQL server 5.1.11-beta and the mysql-connector-java-5.0.3 . This
should work with any 5.0 release, but i haven't validated it.
I checked your tables.sql. You do not use InnoDB option. Without that, the
foreign key constraints can not be enforced. (The reverse engineered tables
have InnoDB turned on) For an enterprise class application, I would prefer
to have data integrity enforced as much as possible.
I wasn't aware that constraints could be used only with InnoDB tables. I
know that they are missing and will port them later (at least after all
the patches have been released). I haven't been able to modify the sql
files you provided (from the reverse engineering) to use an
auto_increment column as primary key it's why i haven't use the files.
Ideally i would like to use the tables as they have been reverse
enginneered and the store procs and views like they have been ported by
my scripts (and my hands :-), but this hasn't been possible yet.
As you may have found, many foreign keys are lacking in current tables.sql.
We will need to improve that part of modeling, if you agree with me on the
InnoDB option.
I wasn't aware that it was missing a lot of foreign keys, only
constraints like cascade delete and so on : i will check.
I have nothing against the InnoDB option, but in my setup this is not
needed (and if i implement Lokahi at work i'm afraid that this will be
on MS SQL server). I guess we can have sql ddl files for the 2 flavors
just by using a ant filter/switch (in the case constraints are also
supported by MyISAM tables -> will check the doc later).
Also we need to find a better way to populate the initial data set,
particularly tmc_user_data.sql and tmc_instance_data.sql.
For me ant filters are fine for the type of deployment i will put in
place (automatic deployment). But effectively this can be nice to do.
Other apps have
used an URL (like install.jsp) to envoke the initialization. This way we do
not have to use sql files to populate them. What's your thought on this?
It's a good idea, and i will help code it, but i would like to finish to
study the application before defining priorities for development :-)
Also, as a system admin in my day to day job, i'm more interested in
making easier the automatic deployment of Lokahi and other apps, with
the less manual intervention possible.
Ok, let's go finish the patches! Ant thanks for you support,
--
Cordialement,
Ludo - http://www.ubik-products.com
---
"L'amour pour principe et l'ordre pour base; le progres pour but" (A.Comte)
