Re: Unable to edit rows in Query Browser - Michael Crowl - com.mysql.lists.win32

10 messages in com.mysql.lists.win32Re: Unable to edit rows in Query Browser

From	Sent On	Attachments
Daniel Bronzeri Barbosa	22 Sep 2004 04:01
Patino, Hernando	22 Sep 2004 05:42
SGr...@unimin.com	22 Sep 2004 06:18
Daniel Bronzeri Barbosa	22 Sep 2004 06:28
Jordan Sparks	22 Sep 2004 07:21
Catapult Webmaster	22 Sep 2004 07:38
Randy Clamons	22 Sep 2004 13:37
Michael Crowl	22 Sep 2004 14:07
Randy Clamons	22 Sep 2004 14:41
Michael Crowl	22 Sep 2004 14:49

Subject:	Re: Unable to edit rows in Query Browser
From:	Michael Crowl (octo...@serv.net)
Date:	09/22/2004 02:49:12 PM
List:	com.mysql.lists.win32

"1. Does your table have a primary key defined?"

BAHHHahahahaha... Why didn't I see that?

Well done. Thank you very much!

-- mike

Randy Clamons wrote:

Mike,

I would need to know a little more about your table structure to give you a
definitive answer to your question. For this reaseon, you might want to include
your table structure information when posting a question.

My first questions would be: 1. Does your table have a primary key defined? 2. Does your query include the primary key?

If your answer is no to either question, that is the problem.

------------Original Message------------ From: Michael Crowl <octo...@serv.net> To: win...@lists.mysql.com Date: Wed, Sep-22-2004 2:11 PM Subject: Unable to edit rows in Query Browser

Problem with MySQL Query Browser on Win2k...

I have an InnoDb table called "linkorderevents", with foreign keys like

an OrderID and EventID. I wanted to throw a couple of sample rows in there - but Edit wouldn't appear for this table. I tried removing the foreign key constraints, and that changed nothing. I can Edit rows in all other tables in the database except for the two tables that started

with "link". I renamed one of them - no change, so that wasn't it. I can, of course, INSERT. I can't think of why this table is producing a

resultset that isn't editable.

Just wondering if anyone has run across this problem... found nothing in the MySQL bugs database.

-- mike