the
> first place.. Just change idrow to auto_increment and stop doing max.. Its
> not needed. innodb properly handles auto_increment now.
>
> Jeff
>
> -Messaggio originale-
> Da: Jeff Smelser [mailto:[EMAIL PROTECTED]
> Inviato: venerd? 4 novembre 2005 16.42
>
stop doing max.. Its
not needed. innodb properly handles auto_increment now.
Jeff
-Messaggio originale-
Da: Jeff Smelser [mailto:[EMAIL PROTECTED]
Inviato: venerdì 4 novembre 2005 16.42
A: mysql@lists.mysql.com
Oggetto: Re: MySQL 5.0 : error using max(idrow) on a null value
On Friday 04 Nov
On Friday 04 November 2005 07:30 am, AESYS S.p.A. [Enzo Arlati] wrote:
> Hi, I'm trying to migrate from MySQL 4.1.11 to MySQL 5.0 and I get a
> problem with the new release.
> I have this table...
>
> provasql
> CREATE TABLE `provasql`
>
> `idrow` bigint(20) unsigned NOT NULL default '0',
> `descr
Hi, I'm trying to migrate from MySQL 4.1.11 to MySQL 5.0 and I get a problem
with the new release.
I have this table...
provasql
CREATE TABLE `provasql`
`idrow` bigint(20) unsigned NOT NULL default '0',
`descr` varchar(50) default NULL,
PRIMARY KEY (`idrow`)
) ENGINE=InnoDB DEFAULT CHARSET=lati