Re: Double conversion error

2004-12-16 Thread Gleb Paharenko
Hello. Update works fine on my 4.1.7-debug-log MySQL instance on Linux. May be you should switch to the latest release. "Berry, Brett C" <[EMAIL PROTECTED]> wrote: > Hello, > > The create table statement is as follows: > > CREATE TABLE `call` ( > `call_id` int(10) unsigned NOT

Re: Double conversion error

2004-12-15 Thread Berry, Brett C
Hello, The create table statement is as follows: CREATE TABLE `call` ( `call_id` int(10) unsigned NOT NULL auto_increment, `init_lband` int(10) unsigned NOT NULL default '0', `chan_assign_sec` tinyint(3) unsigned default NULL, `adn_time_sec` tinyint(3) unsigned default NULL, `setup` cha

Re: Double conversion error

2004-12-14 Thread Gleb Paharenko
Hello. Can you send complete test for your problem (i.e SHOW CREATE TABLE on your tables, buggy sql statement...)? On my 4.1.7 instance of MySQL everything looks fine: mysql> desc v1; +---+-+--+-+-+---+ | Field | Type| Null | Key | Default | Extra | +-

Double conversion error

2004-12-13 Thread Berry, Brett C
Title: Double conversion error I have a query where I perform an update "where (CALL_ID = 2.37000e+002);" This query updates nothing, even though my "CALL_ID" column has an id of "237". If I change the end of this query to read: "where (