MySQL FIX: Row handle referred to a deleted row or a row marked for deletion.
June 27, 2008
Okay, so this could be a few things. Usually this means mysql is trying to access a row that you’ve already deleted. However I happened to get this error just by doing a select statement (and I hadn’t updated or deleted anything — go figure). I believe SQL didn’t like order in which I was selecting the fields. To diagnose the problem I broke the SQL down and gradually added the fields I’d selected back in piece by piece. Once I’d done this everything was fine and dandy.
When I was looking for help on this I found someone else who has having the same problem but the reason for their error message was because the database was in 65 compatability mode. Heh, sounds like a lot of things can give you this problem.
Entry Filed under: Fixes For Errors, MySQL, Programming Languages. .
5 Comments Add your own
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <pre> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed
1.
Nelson | September 17, 2008 at 7:19 am
had the same problem. SQL SERVER 2005.
just a simple join select statement resulted in error like you have.
i found out that my table’s Foreign keys or indexes were gone, maybe some people modified it. So i set F keys and indexes and everything went fine.
2.
Jade | September 17, 2008 at 2:16 pm
Thanks! I appreciate it
3.
Nanny Agency | January 8, 2009 at 7:55 pm
I had the same program when I migrated from MS Access to SQL Server. You have to define primary key in all table of the view.
or Call “select” as a readonly recordset. (adLockReadOnly)
4.
Kalyan | May 11, 2009 at 5:24 am
Thanks for ur info. I had a prob in view while migrating MS 2000 to MS 2005. After i set the Primary key the prob was solved.
5.
Bill Bartmann | September 3, 2009 at 3:26 pm
Cool site, love the info.