List:General Discussion« Previous MessageNext Message »
From:AESYS S.p.A. [Enzo Arlati] Date:November 4 2005 3:56pm
Subject:R: MySQL 5.0 : error using max(idrow) on a null value
View as plain text  

For a while my application should support both mysql 4 and 5 ( teh same copy
on different sites of course ) so I should keep using a soluting wich should
works well on both revision.
I also have a couple of server with their database configured as master
slave, so I don't trust to use autoincrement.
When I can leave ther revision 4 at all I think to use the autoincrement
using a trigger and mybe something like  the oracle sequence  .

regards, Enzo


Mysql 5 is much more picky on things you shouldnt have been able to do in
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:tradergt@stripped]
Inviato: venerdì 4 novembre 2005 16.42
A: mysql@stripped
Oggetto: Re: MySQL 5.0 : error using max(idrow) on a null value


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` varchar(50) default NULL,
> PRIMARY KEY (`idrow`)
> ) ENGINE=InnoDB DEFAULT CHARSET=latin1
>
>
> ...this is the SQL command...
>
> insert into provasql ( idrow, descr )
> select ( select max(c.idrow)+1 from provasql c ) , 'This is only a test';
>
>
> ...and this is the error:
>
> ERROR 1263 (22004): Column set to default value; NULL supplied to NOT NULL
> colum
> n 'idrow' at row 1
>
>
> With MySQL 4.1.11 I'd never get this error message, but it happens with
the
> 5.0.15 version.
> Can anyone help me?

Mysql 5 is much more picky on things you shouldnt have been able to do in
the
first place.. Just change idrow to auto_increment and stop doing max.. Its
not needed. innodb properly handles auto_increment now.

Jeff

Thread
MySQL 5.0 : error using max(idrow) on a null valueAESYS S.p.A. [Enzo Arlati]4 Nov
  • Re: MySQL 5.0 : error using max(idrow) on a null valueJeff Smelser4 Nov
    • R: MySQL 5.0 : error using max(idrow) on a null valueAESYS S.p.A. [Enzo Arlati]4 Nov
      • Re: R: MySQL 5.0 : error using max(idrow) on a null value(Pete Harlan)4 Nov