>-----Original Message----- >From: Sydney Puente [mailto:sydneypue...@yahoo.com] >Sent: Friday, October 30, 2009 10:36 AM >To: mysql@lists.mysql.com >Subject: Re: insert warning - how to look at > >Thanks johan, >Very useful - it seems so obvious now! >There is an associated problem with transferring data into mysql. >because if the application pushing the data finds a warning it just silently >stops. >anyway I can detect a warning 1265 Data truncated on the mysqldb? >and make this visible - at worst I could tail a log file. > [JS] If you can enter the query manually and generate the warning, then you can use the brute force technique that I've used: do a
SELECT ... WHERE LENGTH(...) = [length of troublesome field] By the way, I //think// that you'll get the same message if you try to insert a "bad" character for the character set being used. >TIA > >Syd > > >>Hi, >>mysql> show warnings; > >>BR >>johan > >Sydney Puente wrote: >> Hello, >> >> I have an application which is inserting rows into a Mysql 5.024 db. >> It seems to stop when an insert generates a warning. >> when I insert the suspect line on the mysql commandline I get this: >> Query OK, 1 row affected, 1 warning (0.05 sec) >> Other inserts that succeed seem not to generate warnings when I make the >insertion on >> the command line. >> >> What can I do to troubleshoot this? >> For example how can I access the actual warning? >> >> TIA >> >> Syd >> >> >> >> > > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
