You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Nikolaus Schmitt <n....@scaet.de> on 2001/06/19 04:10:24 UTC
Torque: trimming DB constraint names
DB2 (tested with V7.1 FP3) does not accept names for constraints longer than
18 chars. Using the TDK (2.1b4) as is, the build process will give a hard
time for the unintended, since the security management tables will have
constraints with longer names. I want to ask here for a possibility to add
length limit properties for DB object names into the "project.properties"
file. These delimiters could be used to trim object names exceeding the
limits according to some "trimming rules" realized by velocy macros. IMHO,
it seems to be far easier to "trim" the constraint names by hand for now.
Does the Peer subsys access the constraints of the turbine tables by name in
any way?
My Turbine/DB2 experience of the last days will get assembled into a short
doc, and might get included into the TDK doc and shorten a tiny part of the
learning curve.
----------------------------------------
Nikolaus Schmitt e-mail n.schmitt@scaet.de
Meister-Gerhard-Straße 16 fon +49.221.2406282
50674 Köln fax +49.221.9233901
mobile +49.171.5207498
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Torque: trimming DB constraint names
Posted by John McNally <jm...@collab.net>.
You can specify the name of a sequence used to generate ids for a table.
<table name="SOME_REALLY_LONG_NAME" idMethod="native">
<id-method-parameter value="SRLN_SEQ"/>
...
john mcnally
Daniel Rall wrote:
>
> "Nikolaus Schmitt" <n....@scaet.de> writes:
>
> > DB2 (tested with V7.1 FP3) does not accept names for constraints longer than
> > 18 chars. Using the TDK (2.1b4) as is, the build process will give a hard
> > time for the unintended, since the security management tables will have
> > constraints with longer names. I want to ask here for a possibility to add
> > length limit properties for DB object names into the "project.properties"
> > file. These delimiters could be used to trim object names exceeding the
> > limits according to some "trimming rules" realized by velocy macros. IMHO,
> > it seems to be far easier to "trim" the constraint names by hand for now.
> > Does the Peer subsys access the constraints of the turbine tables by name in
> > any way?
>
> We definitely need a way to define column/constraint name maximum
> lengths per database, and to handle trimming for all names to unique
> values in a consistant manner. Patches welcome, commentary also
> appreciated.
>
> > My Turbine/DB2 experience of the last days will get assembled into a short
> > doc, and might get included into the TDK doc and shorten a tiny part of the
> > learning curve.
>
> Excellent! Please submit a patch based on the appropriate xdoc.
>
> Daniel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Torque: trimming DB constraint names
Posted by Daniel Rall <dl...@finemaltcoding.com>.
"Nikolaus Schmitt" <n....@scaet.de> writes:
> DB2 (tested with V7.1 FP3) does not accept names for constraints longer than
> 18 chars. Using the TDK (2.1b4) as is, the build process will give a hard
> time for the unintended, since the security management tables will have
> constraints with longer names. I want to ask here for a possibility to add
> length limit properties for DB object names into the "project.properties"
> file. These delimiters could be used to trim object names exceeding the
> limits according to some "trimming rules" realized by velocy macros. IMHO,
> it seems to be far easier to "trim" the constraint names by hand for now.
> Does the Peer subsys access the constraints of the turbine tables by name in
> any way?
We definitely need a way to define column/constraint name maximum
lengths per database, and to handle trimming for all names to unique
values in a consistant manner. Patches welcome, commentary also
appreciated.
> My Turbine/DB2 experience of the last days will get assembled into a short
> doc, and might get included into the TDK doc and shorten a tiny part of the
> learning curve.
Excellent! Please submit a patch based on the appropriate xdoc.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org