<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.openoffice.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jeffrobins</id>
	<title>Apache OpenOffice Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.openoffice.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jeffrobins"/>
	<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/wiki/Special:Contributions/Jeffrobins"/>
	<updated>2026-10-18T17:57:16Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.14</generator>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Database/Drivers/MySQL_Native/Known_Problems&amp;diff=83420</id>
		<title>Database/Drivers/MySQL Native/Known Problems</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Database/Drivers/MySQL_Native/Known_Problems&amp;diff=83420"/>
		<updated>2008-06-15T19:02:11Z</updated>

		<summary type="html">&lt;p&gt;Jeffrobins: Added workaround to connect using a socket file that is not located in /tmp&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Existing table fields cannot be altered ===&lt;br /&gt;
The implementation simply didn&amp;#039;t get that far (css.sdbcx.XAlterTable not implemented) ... for the final release, we expect this to be fixed.&lt;br /&gt;
&lt;br /&gt;
=== The user interface is not remotely intuitive ===&lt;br /&gt;
That&amp;#039;s true. The final version will run in OpenOffice.org 3.0 only, which will have a dedicated and thus vastly improved UI.&lt;br /&gt;
=== The driver doesn&amp;#039;t run in OpenOffice.org 3.0 developer snapshots ===&lt;br /&gt;
Well, it&amp;#039;s not intended to do. Please use it with the 2.4 release only, everything else is not supported right now, and may lead to all kinds of unwanted results.&lt;br /&gt;
=== Subforms do not work ===&lt;br /&gt;
Well, some of them do ... more precisely, SQL statements with named parameters (&amp;quot;:param_name&amp;quot;) do not work in general. The ODBC/JDBC driver wrapper used to replace them with unnamed parameters (&amp;quot;?&amp;quot;), since MySQL does not understand them, but the native driver does not do this, yet. Since subforms usually make heavy use of such named parameters, they currently fail.&lt;br /&gt;
=== Specifying a different socket path is not supported (Linux) ===&lt;br /&gt;
Currently, the driver expects the socket to be &amp;lt;code&amp;gt;/tmp/mysql.sock&amp;lt;/code&amp;gt;. This is hard-coded, and will be fixed with new UI (3.0). There are 2 workarounds:&lt;br /&gt;
&lt;br /&gt;
1)  Specify an IP number and a port number, like this: &amp;lt;code&amp;gt;127.0.0.1:3306/yourdb&amp;lt;/code&amp;gt;. In this case the driver will establish a connection via TCP and not a local socket.&lt;br /&gt;
&lt;br /&gt;
2)  Add a link from the real socket file to /tmp/mysql.sock by running this command &amp;quot;ln -s /&amp;lt;path to file&amp;gt;/mysql.sock /tmp/mysql.sock&amp;quot;.  However, this will probably need to be done by the root user and depending on your computer&amp;#039;s settings the /tmp folder may be cleared each time the machine restarts.  Meaning that this must be done after each boot.&lt;br /&gt;
&lt;br /&gt;
=== User administration is offered in the UI, but yields an error when chosen ===&lt;br /&gt;
FILL IN DESCRIPTION&lt;br /&gt;
&lt;br /&gt;
=== Tools&amp;gt;Relations... not working ===&lt;br /&gt;
&lt;br /&gt;
Error message: Database not support relations&lt;/div&gt;</summary>
		<author><name>Jeffrobins</name></author>
	</entry>
</feed>