On Fri, 24 Nov 2000, Stefan Guenther wrote:
> Well, the problem arises from the table scheme in the new security code,
> which uses
> names for database objects, which are longer than 18 chars. Versions of
> Informix before Version 9
> are restricted to 18 chars on db objects, which is, as of a discussion some
> weeks ago on this list, correspondent to the ANSI specs.
>
> Assuming, that the om part of the security system should be completely
> generated by torque sometime in the future, I tried to add functionality to
> shorten the names, generated from Torque, with the addition that the Java
> class names keep its original form. With this functionality it should be
> possible, to generate templates, which transparently shorten the names of db
> objects if necessary.
At some point soon I would like to generate the OM for Turbine
with Torque. Get rid of the static classes and get rid
of TurbineMapBuilder.
So you need to shorten the table names?
> But running into another problem with Informix, i have to look in the source
> of the security-peer-objects, this leads me to the conclusion, that it is
> not planned, to generate this part from templates. So the functionality i am
> trying to add, is probably not necessary, because, for my own project I will
> try to obey the "restrictions" of Informix ;-).
Turbine's OM will be generated by Torque eventually.
> And that lead to the conclusion, that I must change Turbine source by hand
> every time I use a new "version/release" with Informix, if the naming scheme
> is not shortened through the turbine developement process...
>
> Now to the other problem mentioned above, it seems as if Informix converts
> all names for db objects to lower case and requires that queries contains
> the names in lowercase.
Are you sure about that?
> This could be handled the same way as the name length problem, but keeps
> theory as long as if it is not planned or it is not possible to generate the
> om - part of the security system via torque. BTW I have seen this the other
> way round on Interbase, but don't now whether Interbase requires the names
> upper case in queries.
>
> Hope this explains the topic enough to you Jason.
So it's basically a problem with the length of the table names?
For your project specific tables this isn't a problem I assume
because you can make your table names to conform to Informix
and use the javaName attribute to name the java class whatever
you wish.
As far as the Turbine security code goes, I haven't tried to
make Torque generate it yet. But it will happen soon unless
there are some technical reasons why I can't (haven't look
at it in too much detail)
So right now, applying your patch would really help you
would it?
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
