On Fri, Dec 11, 2009 at 8:43 AM, Johan De Meersman <vegiv...@tuxera.be>wrote:
> On Fri, Dec 11, 2009 at 11:19 AM, Mark Goodge <m...@good-stuff.co.uk>
> wrote:
>
> > Jørn Dahl-Stamnes wrote:
> >
> >> On Friday 11 December 2009 10:38, Victor Subervi wrote:
> >>
> >>> Hi;
> >>>
> >>> mysql> update products set sizes="('Small', 'Large')" where ID=0;
> >>> Query OK, 0 rows affected, 1 warning (0.00 sec)
> >>> Rows matched: 1 Changed: 0 Warnings: 1
> >>>
> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> Look at the message, 0 rows changed and 1 warning.
> >> You cannot have ID=0 if ID is an index.
> >>
> >
> > You can, but not if it's an auto-increment field.
> >
>
> Also, not *entirely* correct, although you have to jump through a few
> hoops:
> it can occur if the field was changed to auto_increment *after* the 0 was
> put in there.
>
> Yes, I inherited a database like that once, and yes, it fucks up your day.
>
I'm lost. I set up this database originally with auto_increment and the
first value was 0. I thought that was always the case. Is there a problem
here?
V
