setting oooqa keyword
alex

correcting title
alex

more info : the tables which cause the error message already have data in them.
Other tables, that are as yet free of any data, can be opened. See my comments
in i65572

Just tried writing data via the opened table from within OOo ODB table window.
Error message : illegal operation.

To sum up :
You can't open tables that already have data in them.

You can open tables that don't yet have any data in them.

You can't write new data into these virgin tables.

Alex

Update :

If I insert values via the mysql CLI into a table that previously had no data
stored in it, and then try to access this table via the OOo GUI by opening it
from within an ODB document, I get the same error message as for all the other
tables that already had data in them.

Conclusion : you still can not write data into a table using the MySQL JDBC
connector from OOo Mac OSX PPC m180. Once you write data into a previously empty
table, the table data can no longer be read from within the OOo GUI.

Alex 

works fine with a 3.1.12 JDBC driver on a winxp in a src680m180 

Hi,

I've just now tried this on a Linux box with m180 connecting via MySQL JDBC
Connector 3.1.13 to a remote mysql server, and it works fine.

The problem appears to be Mac specific (yet again, sigh).

Alex 

@alex

Thank you for creating this issue.  Can you connect to a LOCAL database on your
Mac system like I asked you to do in IZ 65572?

James M.

@james : I am going to try and install a local mysql server on the Mac machine,
but disk space is very tight, and I might not have enough room. This is one of
the reasons why we are doing remote access to mysql servers from the Mac boxes.

I'll keep you posted.

Alex

@all : I have installed a mysql server locally on the Mac machine and created
some tables with varying fields in them (INT, AUTO_INCREMENT, VARCHAR,
DATE,etc). I can write to these tables from within OOo m180 using either of the
JDBC drivers, although the 3.1.12 driver doesn't work properly in that it
refuses to display auto_increment fields. The 5.03 JDBC driver works OK in this
regard. Also, the 3.1.12 driver won't display field names with accents in (Latin
characters like é and è), for example like the fields proposed in the OOo Table
Creation Wizard (Contacts). I beleive this was a known limitation of the driver.

Anyway, locally there is write access.

Remote access still results in the Illegal operator message. On the fourth
attempt to access a table that provokes this error message, OOo m180 crashes and
opens the Apple bug reporter.

So, remote access doesn't work, and this is what we use in our production set up.


Alex

@all : I have installed a mysql server locally on the Mac machine and created
some tables with varying fields in them (INT, AUTO_INCREMENT, VARCHAR,
DATE,etc). I can write to these tables from within OOo m180 using either of the
JDBC drivers, although the 3.1.12 driver doesn't work properly in that it
refuses to display auto_increment fields. The 5.03 JDBC driver works OK in this
regard. Also, the 3.1.12 driver won't display field names with accents in (Latin
characters like é and è), for example like the fields proposed in the OOo Table
Creation Wizard (Contacts). I beleive this was a known limitation of the driver.

Anyway, locally there is write access.

Remote access still results in the Illegal operator message. On the fourth
attempt to access a table that provokes this error message, OOo m180 crashes and
opens the Apple bug reporter.

So, remote access doesn't work, and this is what we use in our production set up.


Alex

I might add that updating from the Mac to the remote mysql database works fine
from within CocoaMysql, so it's definitely linked to the way Mac OOo version
uses the MySQL JDBC driver to call the data from the remote server.

Alex

adding crash keyword because if you try to access a table that produces the
error message three or four times in a row, OOo systematically crashes.

Upping priority to P2

Alex

linking to i65572

BTW, the problem is still present in D680_m1

Alex

and still present in 2.0.4rc1

@wurzel:

I have a test version of OpenOffice.org with fixes for some other problems.  I 
will have to setup a test network and see if I can get this error to recur.
I don't have a location where the test version can be retrieved from.

James McKenzie

smsm1 -> wurzel:
Do you have some sample SQL tables that can be used to make testing of this easier?

@smsm1 : here's a sample table definition :

CREATE TABLE citation (
citation_id int(11) unsigned zerofill NOT NULL auto_increment,
family_id int(11) NOT NULL default '0',
citation_ref varchar(100) NOT NULL default '',
majdate timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
PRIMARY_KEY (citation_id)
)
ENGINE=MyISAM DEFAULT CHARSET=Latin1

I can't give you the data, it is covered by my professional secrecy obligations
(attorney client privilege).


Alex

The problem is still there with 2.1rc1, and OOo still crashes after about 5 or 6
unsuccessful attempts to display the remote table

alex

cc'ing fs: Frank, do you know somebody who would be able to debug the scenario which happens also in 
2.1?

This issue may be related to 66123.  More investigation is needed.  

James McKenzie

@wurzel:

There are MySQL ODBC drivers available for the Mac Intel at:
http://www.graphiccare.ca/index.php?option=com_content&task=view&id=56&Itemid=37
I would like to pass my thanks to Thomas Page of Graphic Care for building and
releasing them.
I have not been able to test them with a remote connection.
James McKenzie

> cc'ing fs: Frank, do you know somebody who would be able to debug the
> scenario which happens also in 2.1?

If you in the OOo/Mac community do not know who could debug this, who else
should? :)

If somebody can provide me with a stack of the crash at least, I could have a
look at it (attach it to this issue).

For the error in displaying the tables: If somebody can provide information
about when/where the respective com::sun::star::sdbc::SQLException is thrown
(the debugger should be able to break on this event, and show the stack), this
might also give a hint. Besides this, I'm not sure about the tracing
capabilities of the JDBC drivers. If there were some, you could try looking
what's done last.

@james

Tried the binary MyODBC driver for MacIntel platform you suggested, but it
throws the following error :

[iODBC][DriverManager]
dlopen(/usr/local/myodbc/lib/libmyodbc3_r_3.51.12.so,6)
:Library no loaded : /usr/lib/libltdl.3.dylib
Referenced from : /usr/local/myodbc/lib/libmyodbc3_r_3.51.12.so

Reason : image not found

SQL Status : 00000
Error Code : -1341126392

This was tested on OOo 2.1, I can not install a dev version on the MacIntel
production machine. 


Alex

Removed dependency to an old issue.  This issue is independent of any release
version.

This now works for me in 3.0 Beta m3 Aqua OOo. Setting to resolved, WFM.

Alex

closing