From: Paul DuBois [mailto:[EMAIL PROTECTED]
At 21:09 +0200 6/16/03, Fernando Martins wrote:
In AUTO_INCREMENT fields, inserting a 0 into the field requests a new
sequence number.
Is it possible to turn off this behaviour? (without messing with
the code,
of course)
No.
Using NULL to
At 23:50 +0200 6/18/03, Fernando Martins wrote:
From: Paul DuBois [mailto:[EMAIL PROTECTED]
At 21:09 +0200 6/16/03, Fernando Martins wrote:
In AUTO_INCREMENT fields, inserting a 0 into the field requests a new
sequence number.
Is it possible to turn off this behaviour? (without messing with
Just a note on this subject. We have a field that uses 0 to mean
something special too. It was a bad idea that is on my TODO list to fix
some day. (The corresponding table used 0 to mean something special, and
then joined to the table with the autoindex. The fix is too use null in
that other table
# [EMAIL PROTECTED] / 2003-06-16 21:09:14 +0200:
In AUTO_INCREMENT fields, inserting a 0 into the field requests a new
sequence number.
Is it possible to turn off this behaviour?
I doubt that.
(without messing with the code, of course)
I doubt that some more.
Using NULL to get
At 21:09 +0200 6/16/03, Fernando Martins wrote:
In AUTO_INCREMENT fields, inserting a 0 into the field requests a new
sequence number.
Is it possible to turn off this behaviour? (without messing with the code,
of course)
No.
Using NULL to get the next sequence number is good enough for me and I
