Hello all,
After reading a bit on Catalogs and Schema's, And messing with mysql which
doesn't use the schema's, I had the main idea to remove the hierarchy
between catalogs, schema's and tables.
SQL2Java expects catalogs, schema's and tables to be used in the following
way:
Catalog
+ Schema
+ Table
Instead of doing it this way, I suggest making the Catalog and Schema a
property of a table. In many JDBC drivers, the Schema includes the creator
of the table while the Catalog is a way to combine tables into a logical
unit. Therefor converting them to properties of the table is possible.
I don't know if I'm right saying the following, but isn't it so, we declare
which catalog we'll use when connecting to the database trough the JDBC DSN?
Or am I confused by the terms database and catalog?
Do you think this is a good idea?
Anyway, I am making a lot of changes to the sourcecode inside CVS, including
a proper way to define which tables should be generated and which won't. I
still need to send a request to the eclipse team to request for a proper
plugin to be made. As for now, a Swing gui is being prepared. Filter
settings will be defined inside an XML document, allowing us to save it
between generations. This functionality is meant to replace the current
filter feature using patterns.
Again, Do you think this is a good idea? Or do you prefer the pattern way?
Maybe the best of both worlds and implement both of them?
Please give me some feedback about these issues.
Regards,
Daan
|
