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 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` char(3) NOT NULL default '---', > `setup_sec` tinyint(3) unsigned default NULL, > `completion` char(3) NOT NULL default '---', > `duration_sec` int(10) unsigned default NULL, > `ab_term` char(3) default '---', > `session_id` int(10) unsigned NOT NULL default '0', > `lgc_x` int(11) default NULL, > `lgc_y` int(11) default NULL, > `lgc_z` int(11) default NULL, > PRIMARY KEY (`call_id`), > KEY `FK_session_id` (`session_id`), > CONSTRAINT `call_ibfk_4` FOREIGN KEY (`session_id`) REFERENCES = > `call_session` (`session_id`) > ) ENGINE=3DInnoDB DEFAULT CHARSET=3Dlatin1 COMMENT=3D'InnoDB free: 4096 = > kB' > > > > The row I'm trying to match on is an auto incremented row in an InnoDB = > table. > > The SQL Query is as follows: > > update call set CHAN_ASSIGN_SEC =3D 3, ADN_TIME_SEC =3D 4, SETUP_SEC =3D = > 7, DURATION_SEC =3D 45, AB_TERM =3D 'N', COMPLETION =3D 'Y', SETUP =3D = > 'Y' where (CALL_ID =3D 2.37000000000000000e+002); > > There is indeed a row with call_id=3D237. > > > Regards, > -Brett Berry > > --- > > 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=20 > looks fine: > > mysql> desc v1; > +-------+---------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +-------+---------+------+-----+---------+-------+ > | v | int(11) | YES | | NULL | | > +-------+---------+------+-----+---------+-------+ > select * from v1; > +------+ > | v | > +------+ > | 237 | > +------+ > mysql> select * from v1 where v=3D2.37000000000000000e+002; > +------+ > | v | > +------+ > | 237 | > +------+ > update v1 set v=3D11 where v=3D2.37000000000000000e+002; > select * from v1; > +------+ > | v | > +------+ > | 11 | > +------+ > > >>I have a query where I perform an update "where (CALL_ID =3D >> 2.37000000000000000e+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 (CALL_ID =3D 237);", = > then the row >> with >>"CALL_ID=3D237" is updated. >> >>Is there a reason why the double value "2.37000000000000000e+002" is = > not evaluating >> to >>"237"? >> >>Regards, >>-Brett Berry > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
