in reply to Re: Using placeholders, getting unexpected SQL errors
in thread Using placeholders, getting unexpected SQL errors
I took your advice and traced the bastard, which showed me how MySQL was choking (even after using bind_param), if you will:if (($row->{'cust_phpx'} != '') && ($row->{'cust_phsx'} != '')) { # # Execute the query # }
On a lark I replaced the "!=" in the if test with "ne". No more errors. I don't get it. It seems like the comparison operator "fiddled with the nature" of the variable it was operating on. Whatever that means. By the way check this out. See the fifth bugfix for v.053. (This has nothing to do with the code I'm working on, I don't even know what "WeSQL" is, but when I desperately googled for answers, I found this). Something smells fishy...I hope it's just my lunch.-> execute for DBD::mysql::st (DBI::st=HASH(0x8218138)~0x82180b4 ' +3048770' '2' '1' '704' 53 2 89 '45') -> dbd_st_execute for 082180a8 Binding parameters: INSERT INTO PhoneNumbers (cusID, adtID, pntI +D, phnPart1, phnPart2, phnPart3, phnExt) VALUES ('3048770', '2', '1', '704', 53, 2 89, '45') ERROR EVENT 1064 'You have an error in your SQL syntax near '89, ' +45')' at line 2' on DBI::st=HASH(0x82180b4)
|
|---|