Your message dated Sat, 8 Jan 2005 08:22:02 +1100
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Re: Bug#289058: OOo - MySQL - ODBC - Cannot
edit tables]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 6 Jan 2005 23:16:13 +0000
>From [EMAIL PROTECTED] Thu Jan 06 15:16:13 2005
Return-path: <[EMAIL PROTECTED]>
Received: from europa.telenet-ops.be [195.130.132.60]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CmgrV-0006HS-00; Thu, 06 Jan 2005 15:16:13 -0800
Received: from localhost (localhost.localdomain [127.0.0.1])
by europa.telenet-ops.be (Postfix) with SMTP id C8FD219805F
for <[EMAIL PROTECTED]>; Fri, 7 Jan 2005 00:16:11 +0100 (MET)
Received: from seven.home.net (D5E0CBEF.kabel.telenet.be [213.224.203.239])
by europa.telenet-ops.be (Postfix) with ESMTP id BBC69198012
for <[EMAIL PROTECTED]>; Fri, 7 Jan 2005 00:16:11 +0100 (MET)
From: freddy <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: OOo - MySQL - ODBC - Cannot edit tables
Date: Fri, 7 Jan 2005 00:16:11 +0100
User-Agent: KMail/1.7.1
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_01,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: openoffice.org
Version: 1.1.3-4
I'm using unixodbc version 2.2.4-11, with MySql 4.0.20-7. I can connect to the
database from OOo, read the data, submit queries and so on, but I cannot
edit the data: the tables are read-only. All the buttons for editing the
fields are greyed out. Earlier discussions on the OOo user mailing list
suggested that this problem is Debian-specific.
---------------------------------------
Received: (at 289058-done) by bugs.debian.org; 7 Jan 2005 21:22:15 +0000
>From [EMAIL PROTECTED] Fri Jan 07 13:22:15 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mailhost.netspeed.com.au [203.31.48.33]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cn1Yl-0002gR-00; Fri, 07 Jan 2005 13:22:15 -0800
Received: from biglin (unverified [210.9.230.71])
by netspeed.com.au (SurgeMail 2.2d) with ESMTP id 2548679
for <[EMAIL PROTECTED]>; Sat, 08 Jan 2005 08:21:47 +1100
Received: from jim by biglin with local (Exim 3.36 #1 (Debian))
id 1Cn1YY-0008U5-00
for <[EMAIL PROTECTED]>; Sat, 08 Jan 2005 08:22:02 +1100
Date: Sat, 8 Jan 2005 08:22:02 +1100
To: [EMAIL PROTECTED]
Subject: [EMAIL PROTECTED]: Re: Bug#289058: OOo - MySQL - ODBC - Cannot edit
tables]
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
From: Jim Watson <[EMAIL PROTECTED]>
X-Server: High Performance Mail Server - http://surgemail.com
X-DNS-Paranoid: DNS ptr lookup of (210.9.230.71) failed
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
----- Forwarded message from Freddy Van Ingelgom <[EMAIL PROTECTED]> -----
Date: Fri, 07 Jan 2005 22:07:33 +0100
From: Freddy Van Ingelgom <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#289058: OOo - MySQL - ODBC - Cannot edit tables
Hello Jim,
Thanks for reply. I have read the information, and adjusted the primary
keys in my database and ... voil?, its working!!!
The (strange) problem was that, when inspecting the table via phpMyAdmin
I saw that my primary key was present twice, plus it was selected as an
index. After deleting the extra occurances it worked. However, within
OOo the field was just marked as a primary key, hence the confusion.
Have a nice weekend, and thanks again for the quick reply.
Freddy
[EMAIL PROTECTED] wrote:
>Freddy,
>
>please have a look at the notes here, especially about PRIMARY KEY and
>report results?
>
>http://dba.openoffice.org/FAQ/specific.html
>
>
>
>
>
>
>
----- End forwarded message -----
