db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Hilka" <thi...@vps.de>
Subject AW: Datatype mapping in Torque 3.2
Date Tue, 18 Jul 2006 12:41:18 GMT

I tried to follow your suggestions. But I still have some problems with
creating my own database settings.

I extended the platform class, changed the torque.database property in my
build.properties (using ant). Now I put the new class in the same .jar as
the other platform classes. The class is found by ant loader. So far so good.

The problem is, now I obviously need a completely new directory structure in the torque templates
for my new Database class. (sql/base/mynewmssql/..., id-table.mynewmssql an so on). Is there
a possibility to use the old structure of the database I extended or do I have to copy them
with new names in the various directories?

Thanks you for your help.


-----Urspr√ľngliche Nachricht-----
Von: Thomas Fischer [mailto:tfischer@apache.org] 
Gesendet: Sonntag, 16. Juli 2006 12:58
An: Apache Torque Developers List
Betreff: Re: Datatype mapping in Torque 3.2

On Sun, 16 Jul 2006, Thomas Vandahl wrote:

> Thomas Fischer wrote:
>> - extend the platform class you want to change, and end the classname 
>> with Impl. Put the resulting class in the same
>> (org.apache.torque.engine.platform.Platform) package.
>> - set the torque.database property in the project.properties (NOT in 
>> the Torque.properties in the runtime, this should stay as it is) to 
>> the Classname without the "Impl" in the end (you may start lowercase)
> One comment about this. As you know, I try to collect the database 
> specific features in the database adapters. The platform 
> implementation, however, is part of the generator and contains 
> database specific stuff, too. Does that make sense? Wouldn't it be 
> better to combine them both in one database specific class?

Not so sure about this.
- The information about the database needed in the generator and in the
runtime are different, so the only benefit would be to have one class
instead of two
- the build process would be complicated, as the class would have to be
delievered in the runtime and the generator


To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message