Error 139 appears to be some kind of bug http://bugs.mysql.com/bug.php?id=10035
Its occurring with a legacy form. Originally error would throw if upload attachment. Changed InnoDB to MyISAM and upload went fine Now if modify text box in form throws same error. Considering switching to MSSQL if cant resolve Any thoughts would be appreciated -----Original Message----- From: Pete Freitag [mailto:p...@foundeo.com] Sent: 2010-10-15 13:23 To: cf-talk Subject: Re: SQL 139 transaction error Since MyISAM is a non-transactional storage engine, the error doesn't make too much sense to me. Are you sure your migration from InnoDB was successful, and that you are infact using MyISAM and not InnoDB on this table? -- Pete Freitag http://foundeo.com/ - ColdFusion Consulting & Products http://petefreitag.com/ - My Blog http://hackmycf.com - Is your ColdFusion Server Secure? On Fri, Oct 15, 2010 at 10:34 AM, cfcom <cf...@aceligent.com> wrote: > > Is anyone familiar with MySql 139 transaction storage error. > I've switched the engine from InnoDB to MyISAM but am still seeing issues. > Am running MySql 5. Am wondering if I should move from open source to a > different DB - Any suggestions or insight would be most appreciated. > > TIA > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:338240 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
