Actually thats not quite right, at least not in my experience. I ran into this when I upgraded to mySQL5 from mySQL4. The fix is twofold.
1: Get a different JDBC driver. Honestly I forget which but you can research this a little better and find the proper one. It is actually NOT the latest one as I recall. The way I tracked down the problem and the solution description was to google up the weirdo number that was being returned by mySQL and handed to me in my error handling code. 2. Remove the "unsigned" parameter everywhere you are using an integer-type field. If its a size overflow then Cutter's solution may in fact be another way to fix the same problem. For me that wasn't an option as I would have also had to change about a zillion cfqueryparam statements in code on dozens of web sites. -- [EMAIL PROTECTED] Janitor, MSB Web Systems mysecretbase.com On 11/13/06, Emil Gudmundsson <[EMAIL PROTECTED]> wrote: > >It's an odd issue with the JDBC driver, you will not get the error if > >you change you autonumber primary key to a bigint. > > > >Cutter > >_______________ > >http://blog.cutterscrossing.com > > > > So it will be better if i find a new JDBC driver? > If the issue is fixed that is. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:260253 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
