"Ferruh Zamangoer" <[EMAIL PROTECTED]> writes:
>Hi Tino,
>I know Hennings posting, but the problem is that the option autoincrement is
>deprecated in torque-gen-3.1, I also know that the option is not removed
>from this package I can use it, but I do not prefer it because I don't know
>what can be occure in later version for example when autoincrement option is
>removed????
As I said. If you can make a case where "autoincrement" is useful, we
might simply remove the deprecation.
The deprecation comes from a time where "sequence", "autoincrement"
and everything else were planned to be faded out in favor of "native"
(which IMHO sucks).
"autoincrement" is in fact a misnomer. This should be
"database-handled" or something like this.
If it works for you: use it. It will _definitely_ not removed for the
3.1 tree (3.1, 3.1.1, 3.1.2 and so on) and this already makes a strong
case for keeping this (maybe renamed) in 3.2.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honorable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
