To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104584
                 Issue #|104584
                 Summary|creating a new MySQL/Native database document leaves a
                        | "UseJava=true" artifact in the content.xml
               Component|Database access
                 Version|DEV300m52
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|none
             Assigned to|fs
             Reported by|fs





------- Additional comments from [email protected] Fri Aug 28 11:10:01 +0000 
2009 -------
- install the Sun MySQL Connector/OOo from
  http://extensions.services.openoffice.org/project/mysql_connector
- File / New / Database
- create a new database using the connector ("MySQL" on the first page,
  "Connect native" on the second page)
- let the wizard save this document
- unzip the .odb file
- view into the content.xml file
=> you'll find a "data source setting" named "UseJava", set to "true".

This is nonsense for two reasons: First, the native driver does not use Java at
all. Second, "UseJava" is a driver meta data, not a data source property. That
is, for a driver (e.g. database type), it can be specified in the configuration
whether it uses Java. The data source settings in the content.xml, however,
apply to a concrete data source, and here a driver meta data as "UseJava" does
not make sense.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to