Apache OpenOffice Wiki - User contributions [en]

Build Environment Effort/Module Status

2011-04-14T09:07:36Z

Oj:

{| cellspacing="0" cellpadding="3" border="1"
|-
| module
| migrated in CWS
| integrated in
| remarks

|-
| accessibility
|
|
|

|-
| afms
|
|
|

|-
| agg
|
|
|

|-
| animations
|
|
|

|-
| apache-commons
|
|
|

|-
| apple_remote
|
|
|

|-
| autodoc
|
|
|

|-
| automation
|
|
|

|-
| avmedia
|
|
|

|-
| basctl
|
|
|

|-
| basebmp
| {{CWS|gnumake4}}
|
| needed fixing of exported symbols

|-
| basegfx
| {{CWS|gnumake4}}
|
| needed fixing of exported symbols

|-
| basic
|
|
|

|-
| bean
|
|
|

|-
| beanshell
|
|
|

|-
| berkeleydb
|
|
|

|-
| binaryurp
| {{CWS|sb143}}
|
|

|-
| binfilter
|
|
|

|-
| boost
|
|
|

|-
| bridges
|
|
|

|-
| cairo
|
|
|

|-
| canvas
| {{CWS|gnumake4}}
|
| needed fixing of exported symbols

|-
| chart2
|
|
|

|-
| cli_ure
|
|
|

|-
| codemaker
|
|
|

|-
| comphelper
| gnumake3
| DEV300m100
|

|-
| configmgr
| {{CWS|sb143}}
|
|

|-
| connectivity
|
|
|

|-
| cosv
|
|
|

|-
| cppcanvas
| {{CWS|gnumake4}}
|
|

|-
| cppu
|
|
|

|-
| cppuhelper
|
|
|

|-
| cppunit
|
|
|

|-
| cpputools
|
|
|

|-
| crashrep
|
|
|

|-
| cui
|
|
|

|-
| curl
|
|
|

|-
| dbaccess
| {{CWS|gnumake4}}
|
|

|-
| default_images
|
|
|

|-
| desktop
|
|
|

|-
| dictionaries
|
|
|

|-
| drawinglayer
| impress212
|
|

|-
| dtrans
|
|
|

|-
| editeng
| gnumake3
| DEV300m100
|

|-
| embeddedobj
|
|
|

|-
| embedserv
|
|
|

|-
| epm
|
|
|

|-
| eventattacher
|
|
|

|-
| expat
|
|
|

|-
| extensions
|
|
|

|-
| external
|
|
|

|-
| external_images
|
|
|

|-
| extras
|
|
|

|-
| fileaccess
|
|
|

|-
| filter
|
|
|

|-
| forms
| [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Ffs35a CWS fs35a]
|
|

|-
| formula
| {{CWS|oj22}}
|
|

|-
| fpicker
|
|
|

|-
| framework
| gnumake2
| DEV300m96
|

|-
| graphite
|
|
|

|-
| helpcontent2
|
|
|

|-
| hsqldb
|
|
|

|-
| hunspell
|
|
|

|-
| hwpfilter
|
|
|

|-
| hyphen
|
|
|

|-
| i18npool
|
|
|

|-
| i18nutil
|
|
|

|-
| icc
|
|
|

|-
| icu
|
|
|

|-
| idl
| {{CWS|gnumake4}}
|
|

|-
| idlc
|
|
|

|-
| instsetoo_native
|
|
|

|-
| io
|
|
|

|-
| javainstaller
|
|
|

|-
| javaunohelper
|
|
|

|-
| jfreereport
|
|
|

|-
| jpeg
|
|
|

|-
| jurt
|
|
|

|-
| jvmaccess
|
|
|

|-
| jvmfwk
|
|
|

|-
| l10n
|
|
|

|-
| l10ntools
|
|
|

|-
| libegg
|
|
|

|-
| libtextcat
|
|
|

|-
| libwpd
|
|
|

|-
| libxml2
|
|
|

|-
| libxmlsec
|
|
|

|-
| libxslt
|
|
|

|-
| lingucomponent
|
|
|

|-
| linguistic
| {{CWS|gnumake4}}
|
| needed fixing of exported symbols

|-
| lpsolve
|
|
|

|-
| lucene
|
|
|

|-
| mathmldtd
|
|
|

|-
| mdds
|
|
|

|-
| migrationanalysis
|
|
|

|-
| more_fonts
|
|
|

|-
| moz
|
|
|

|-
| mysqlc
|
|
|

|-
| mysqlcppconn
|
|
|

|-
| mythes
|
|
|

|-
| neon
|
|
|

|-
| np_sdk
|
|
|

|-
| nss
|
|
|

|-
| o3tl
|
|
|

|-
| odk
|
|
|

|-
| offapi
| ause130
|
| in progress

|-
| officecfg
|
|
|

|-
| offuh
| ause130
|
| in progress; will become obsolete

|-
| ooo_custom_images
|
|
|

|-
| oovbaapi
|
|
|

|-
| oox
| {{CWS|writerfilter10}}
|
| in progress

|-
| openssl
|
|
|

|-
| package
|
|
|

|-
| packimages
|
|
|

|-
| padmin
| vcl118
| DEV300m101
|

|-
| postprocess
|
|
|

|-
| psprint_config
|
|
|

|-
| python
|
|
|

|-
| pyuno
|
|
|

|-
| qadevooo
|
|
|

|-
| rdbmaker
|
|
|

|-
| readlicense_oo
|
|
|

|-
| redland
|
|
|

|-
| regexp
| {{CWS|gnumake4}}
|
| name of library was changed

|-
| registry
|
|
|

|-
| remotebridges
|
|
|

|-
| reportbuilder
|
|
|

|-
| reportdesign
| {{CWS|gnumake4}}
|
|

|-
| rhino
|
|
|

|-
| ridljar
|
|
|

|-
| rsc
|
|
|

|-
| sal
|
|
|

|-
| salhelper
|
|
|

|-
| sane
|
|
|

|-
| sax
| {{CWS|gnumake4}}
|
| sax.uno lib renamed to expwrap.uno because new build system can't separate it from sax library

|-
| saxon
|
|
|

|-
| sc
|
|
|

|-
| scaddins
|
|
|

|-
| sccomp
|
|
|

|-
| scp2
|
|
|

|-
| scripting
|
|
|

|-
| sd
| sd2gbuild
|
|

|-
| sdext
|
|
|

|-
| setup_native
|
|
|

|-
| sfx2
| gnumake2
| DEV300m96
|

|-
| shell
|
|
|

|-
| slideshow
|
|
|

|-
| smoketestoo_native
|
|
|

|-
| soldep
|
|
| will be removed

|-
| soltools
|
|
|

|-
| sot
| gnumake3
| DEV300m100
|

|-
| starmath
| {{CWS|gnumake4}}
|
|

|-
| stax
|
|
|

|-
| stlport
|
|
|

|-
| stoc
|
|
|

|-
| store
|
|
|

|-
| svl
| gnumake2
| DEV300m96
|

|-
| svtools
| gnumake2
| DEV300m96
|

|-
| svx
| gnumake3
| DEV300m100
| special treatment for globlmn.hrc, srs in solver

|-
| sw
| gnumake2
| DEV300m96
|

|-
| swext
|
|
|

|-
| sysui
|
|
|

|-
| test
|
|
|

|-
| testautomation
|
|
| does not build anything

|-
| testgraphical
|
|
|

|-
| testtools
|
|
|

|-
| tomcat
|
|
|

|-
| toolkit
| gnumake2
| DEV300m96
|

|-
| tools
| gnumake2
| DEV300m96
|

|-
| twain
|
|
|

|-
| ucb
|
|
|

|-
| ucbhelper
| {{CWS|gnumake4}}
|
|

|-
| udkapi
| ause130
|
| in progress

|-
| udm
|
|
|

|-
| unixODBC
|
|
|

|-
| UnoControls
|
|
|

|-
| unodevtools
|
|
|

|-
| unoil
|
|
|

|-
| unotools
| {{CWS|gnumake4}}
|
|

|-
| unoxml
| xmlfix3
| DEV300m102
|

|-
| ure
|
|
|

|-
| uui
|
|
|

|-
| vbaapi
| ause130
|
| in progress

|-
| vbahelper
| {{CWS|gnumake4}}
|
|

|-
| vcl
| vcl2gnumake
| DEV300m105
| done; added support for native windows resources

|-
| vigra
|
|
|

|-
| vos
|
|
|

|-
| wizards
| {{CWS|gnumake4}}
|
| added support for zip and jar targets

|-
| writerfilter
| {{CWS|writerfilter10}}
|
|

|-
| writerperfect
|
|
|

|-
| x11_extensions
|
|
|

|-
| xmerge
|
|
|

|-
| xml2cmp
|
|
|

|-
| xmlhelp
|
|
|

|-
| xmloff
| gnumake2
| DEV300m96
|

|-
| xmlreader
| {{CWS|gnumake4}}
|
|

|-
| xmlscript
| {{CWS|gnumake4}}
|
|

|-
| xmlsecurity
|
|
|

|-
| xpdf
|
|
|

|-
| xsltml
|
|
|

|-
| zlib
|
|
|

|}

Build Environment Effort/Module Status

2011-04-05T05:32:50Z

Oj:

{| cellspacing="0" cellpadding="3" border="1"
|-
| module
| migrated in CWS
| integrated in
| remarks

|-
| accessibility
|
|
|

|-
| afms
|
|
|

|-
| agg
|
|
|

|-
| animations
|
|
|

|-
| apache-commons
|
|
|

|-
| apple_remote
|
|
|

|-
| autodoc
|
|
|

|-
| automation
|
|
|

|-
| avmedia
|
|
|

|-
| basctl
|
|
|

|-
| basebmp
| {{CWS|gnumake4}}
|
| needed fixing of exported symbols

|-
| basegfx
| {{CWS|gnumake4}}
|
| needed fixing of exported symbols

|-
| basic
|
|
|

|-
| bean
|
|
|

|-
| beanshell
|
|
|

|-
| berkeleydb
|
|
|

|-
| binaryurp
| {{CWS|sb143}}
|
|

|-
| binfilter
|
|
|

|-
| boost
|
|
|

|-
| bridges
|
|
|

|-
| cairo
|
|
|

|-
| canvas
| {{CWS|gnumake4}}
|
| needed fixing of exported symbols

|-
| chart2
|
|
|

|-
| cli_ure
|
|
|

|-
| codemaker
|
|
|

|-
| comphelper
| gnumake3
| DEV300m100
|

|-
| configmgr
| {{CWS|sb143}}
|
|

|-
| connectivity
|
|
|

|-
| cosv
|
|
|

|-
| cppcanvas
| {{CWS|gnumake4}}
|
|

|-
| cppu
|
|
|

|-
| cppuhelper
|
|
|

|-
| cppunit
|
|
|

|-
| cpputools
|
|
|

|-
| crashrep
|
|
|

|-
| cui
|
|
|

|-
| curl
|
|
|

|-
| dbaccess
|
|
|

|-
| default_images
|
|
|

|-
| desktop
|
|
|

|-
| dictionaries
|
|
|

|-
| drawinglayer
| impress212
|
|

|-
| dtrans
|
|
|

|-
| editeng
| gnumake3
| DEV300m100
|

|-
| embeddedobj
|
|
|

|-
| embedserv
|
|
|

|-
| epm
|
|
|

|-
| eventattacher
|
|
|

|-
| expat
|
|
|

|-
| extensions
|
|
|

|-
| external
|
|
|

|-
| external_images
|
|
|

|-
| extras
|
|
|

|-
| fileaccess
|
|
|

|-
| filter
|
|
|

|-
| forms
| [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Ffs35a CWS fs35a]
|
|

|-
| formula
| {{CWS|oj22}}
|
|

|-
| fpicker
|
|
|

|-
| framework
| gnumake2
| DEV300m96
|

|-
| graphite
|
|
|

|-
| helpcontent2
|
|
|

|-
| hsqldb
|
|
|

|-
| hunspell
|
|
|

|-
| hwpfilter
|
|
|

|-
| hyphen
|
|
|

|-
| i18npool
|
|
|

|-
| i18nutil
|
|
|

|-
| icc
|
|
|

|-
| icu
|
|
|

|-
| idl
| {{CWS|gnumake4}}
|
|

|-
| idlc
|
|
|

|-
| instsetoo_native
|
|
|

|-
| io
|
|
|

|-
| javainstaller
|
|
|

|-
| javaunohelper
|
|
|

|-
| jfreereport
|
|
|

|-
| jpeg
|
|
|

|-
| jurt
|
|
|

|-
| jvmaccess
|
|
|

|-
| jvmfwk
|
|
|

|-
| l10n
|
|
|

|-
| l10ntools
|
|
|

|-
| libegg
|
|
|

|-
| libtextcat
|
|
|

|-
| libwpd
|
|
|

|-
| libxml2
|
|
|

|-
| libxmlsec
|
|
|

|-
| libxslt
|
|
|

|-
| lingucomponent
|
|
|

|-
| linguistic
| {{CWS|gnumake4}}
|
| needed fixing of exported symbols

|-
| lpsolve
|
|
|

|-
| lucene
|
|
|

|-
| mathmldtd
|
|
|

|-
| mdds
|
|
|

|-
| migrationanalysis
|
|
|

|-
| more_fonts
|
|
|

|-
| moz
|
|
|

|-
| mysqlc
|
|
|

|-
| mysqlcppconn
|
|
|

|-
| mythes
|
|
|

|-
| neon
|
|
|

|-
| np_sdk
|
|
|

|-
| nss
|
|
|

|-
| o3tl
|
|
|

|-
| odk
|
|
|

|-
| offapi
| ause130
|
| in progress

|-
| officecfg
|
|
|

|-
| offuh
| ause130
|
| in progress; will become obsolete

|-
| ooo_custom_images
|
|
|

|-
| oovbaapi
|
|
|

|-
| oox
| {{CWS|writerfilter10}}
|
| in progress

|-
| openssl
|
|
|

|-
| package
|
|
|

|-
| packimages
|
|
|

|-
| padmin
| vcl118
| DEV300m101
|

|-
| postprocess
|
|
|

|-
| psprint_config
|
|
|

|-
| python
|
|
|

|-
| pyuno
|
|
|

|-
| qadevooo
|
|
|

|-
| rdbmaker
|
|
|

|-
| readlicense_oo
|
|
|

|-
| redland
|
|
|

|-
| regexp
| {{CWS|gnumake4}}
|
| name of library was changed

|-
| registry
|
|
|

|-
| remotebridges
|
|
|

|-
| reportbuilder
|
|
|

|-
| reportdesign
|
|
|

|-
| rhino
|
|
|

|-
| ridljar
|
|
|

|-
| rsc
|
|
|

|-
| sal
|
|
|

|-
| salhelper
|
|
|

|-
| sane
|
|
|

|-
| sax
| {{CWS|gnumake4}}
|
| sax.uno lib renamed to expwrap.uno because new build system can't separate it from sax library

|-
| saxon
|
|
|

|-
| sc
|
|
|

|-
| scaddins
|
|
|

|-
| sccomp
|
|
|

|-
| scp2
|
|
|

|-
| scripting
|
|
|

|-
| sd
| sd2gbuild
|
|

|-
| sdext
|
|
|

|-
| setup_native
|
|
|

|-
| sfx2
| gnumake2
| DEV300m96
|

|-
| shell
|
|
|

|-
| slideshow
|
|
|

|-
| smoketestoo_native
|
|
|

|-
| soldep
|
|
| will be removed

|-
| soltools
|
|
|

|-
| sot
| gnumake3
| DEV300m100
|

|-
| starmath
| {{CWS|gnumake4}}
|
|

|-
| stax
|
|
|

|-
| stlport
|
|
|

|-
| stoc
|
|
|

|-
| store
|
|
|

|-
| svl
| gnumake2
| DEV300m96
|

|-
| svtools
| gnumake2
| DEV300m96
|

|-
| svx
| gnumake3
| DEV300m100
| special treatment for globlmn.hrc, srs in solver

|-
| sw
| gnumake2
| DEV300m96
|

|-
| swext
|
|
|

|-
| sysui
|
|
|

|-
| test
|
|
|

|-
| testautomation
|
|
| does not build anything

|-
| testgraphical
|
|
|

|-
| testtools
|
|
|

|-
| tomcat
|
|
|

|-
| toolkit
| gnumake2
| DEV300m96
|

|-
| tools
| gnumake2
| DEV300m96
|

|-
| twain
|
|
|

|-
| ucb
|
|
|

|-
| ucbhelper
| {{CWS|gnumake4}}
|
|

|-
| udkapi
| ause130
|
| in progress

|-
| udm
|
|
|

|-
| unixODBC
|
|
|

|-
| UnoControls
|
|
|

|-
| unodevtools
|
|
|

|-
| unoil
|
|
|

|-
| unotools
| {{CWS|gnumake4}}
|
|

|-
| unoxml
| xmlfix3
| DEV300m102
|

|-
| ure
|
|
|

|-
| uui
|
|
|

|-
| vbaapi
| ause130
|
| in progress

|-
| vbahelper
| {{CWS|gnumake4}}
|
|

|-
| vcl
| vcl2gnumake
| DEV300m105
| done; added support for native windows resources

|-
| vigra
|
|
|

|-
| vos
|
|
|

|-
| wizards
| {{CWS|gnumake4}}
|
| added support for zip and jar targets

|-
| writerfilter
| {{CWS|writerfilter10}}
|
|

|-
| writerperfect
|
|
|

|-
| x11_extensions
|
|
|

|-
| xmerge
|
|
|

|-
| xml2cmp
|
|
|

|-
| xmlhelp
|
|
|

|-
| xmloff
| gnumake2
| DEV300m96
|

|-
| xmlreader
| {{CWS|gnumake4}}
|
|

|-
| xmlscript
| {{CWS|gnumake4}}
|
|

|-
| xmlsecurity
|
|
|

|-
| xpdf
|
|
|

|-
| xsltml
|
|
|

|-
| zlib
|
|
|

|}

Base/New features in 3 3

2010-10-29T08:06:22Z

Oj: /* Base in general */

= New features in OOo 3.3 Base =
== Base in general ==
New features "under the hood"

=== Allow to overrule Base's heuristics for primary key support ===
There's a new option "Supports primary keys" in the Advanced Settings of a database, which is to overrule Base's heuristics used to detect whether the database it connects to supports primary keys.

This new option is available for database connections via ODBC, JDBC, and ADO.

[[Image:Supports_pk.PNG]]

When connecting to a database via a generic API like ODBC, JDBC, ADO, Base currently applies a heuristics to determine whether or not this database supports primary keys, because none of those APIs has dedicated support to retrieve this information.

Since the heuristics sometimes fails, there's now an explicit option (Edit / Database / Advanced Settings) named "Supports primary keys". It's implemented as a usual tri-state check box, where un/check mean "do (not) assume PK support", and the "undetermined" third state, which is the default, means "apply the heuristics".

Note that if this option is just for overruling the heuristics. If you check it for a database which actually does not support primary keys, you'll probably be slain with error messages as soon as Base attempts to actually use PK related features (like creating a PK in the table designer).
=== Base now supports updates on more than one table ===
Base now supports updates on more than one table.

Updates are only possible when the row can be fetched right after it was inserted/updated to get all default or changed values by the underlying database. To allow updates on a query on more then one table, all primary keys (all columns which are part of the primary keys) must be in the select list. Base now checks which prerequisite exists and then decide if the query is modifiable or not.

=== Base now supports database registrations configured as read-only ===
Base now supports database registrations which are declared as read-only.

Database registrations are normally maintained via Tools/Options/Databases. The registrations are stored in OpenOffice.org's configuration, which means it is also possible to deploy additional configuration fragments (e.g. via extensions) which contain additional registrations. If those configuration fragments are declared as read-only (by using the usual configuration mechanisms for this), then the UI now respects this, by disallowing modifications (editions, removal) of this registration entry.

=== Extending database drivers by extension ===
Detailed information can be found here:

http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Extending_Database_Drivers

From linked specification:

Extending existing SDBC drivers by [http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions extensions] is described here, Most drivers miss to support special features like to alter view definitions or to add or drop key of a table. Therefor these interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

can be implemented by an extension.

To enable the needed feature the extension has to extend the properties entry of the configuration of the driver. The configuration entry below the properties entry will be checked and if the service name can be instantiated it will be used to do the job. Below you'll see a table of mapping from configuration entry to service name.

Configuration name Interface name which has to to be implemented

ViewSupportServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XViewSupport.html com.sun.star.sdb.tools.XViewSupport]

TableAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableAlteration.html com.sun.star.sdb.tools.XTableAlteration]

TableRenameServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XTableRename.html com.sun.star.sdb.tools.XTableRename]

IndexAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XIndexAlteration.html com.sun.star.sdb.tools.XIndexAlteration]

KeyAlterationServiceName [http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/tools/XKeyAlteration.html com.sun.star.sdb.tools.XKeyAlteration]

In favor to allow to get the definition of queries, forms and reports from other locations as the default file format specification, an extension may implement a service which implement the following named interfaces.

The configuration entries are named
* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier

which all have to implement the interfaces

* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameAccess.html com.sun.star.container.XNameAccess]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XNameContainer.html com.sun.star.container.XNameContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/ucb/XContent.html com.sun.star.ucb.XContent]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XChild.html com.sun.star.container.XChild]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainer.html com.sun.star.container.XContainer]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/container/XContainerApproveBroadcaster.html com.sun.star.container.XContainerApproveBroadcaster]
* [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XInitialization.html com.sun.star.lang.XInitialization]

== Forms ==
=== Ctrl+F5 now toggles between the document and the nearest form control ===
Ctrl+F5, which used to focus the first (by a definition which is hard to understand by the average user) form control in a document, has changed its behavior: It now focuses the form control nearest to the current cursor position, if the focus is not within a form control currently. Otherwise, it gives the focus back to the document view.

=== Form controls use the same text rendering as the containing document ===
This new feature does not really belong to Base only.

The way how controls render their text has changed. Well, this applies to some controls, in some documents, at least.

In general, the OOo applications format their text on the screen using a so-called reference device, which might either be the printer selected for the document, or a virtual device (which one is controlled by a per-document option).

Form controls previously never participated in this game, they always formatted their text according to the screen they were displayed on. As a consequence, form controls which were embedded in the text flow of the containing document broke the document layout when viewed on different devices (print preview, printer, PDF export), or even only when viewed in different zoom levels on the screen.

Now, non-input form controls (radio buttons, fixed texts, check boxes, group boxes, command buttons) use the document's reference device for rendering their own text, thus providing a better integration into the surrounding document text.

This behavior can be enabled on a per-application level, more precise, on a per-module level. There's no UI for changing the behavior.

Instead, the existing configuration structure below the
/org.openoffice.Office.Common/Forms/ControlLayout has been extended, so that now for instance the node .../ControlLayout/com.sun.star.sheet.SpreadsheetDocument/UseDocumentTextMetrics

controls whether the reference device text rendering for controls is enabled in spreadsheet documents.

By default, the usage of the document's reference device is enabled for text documents, drawings, and presentations, and disabled for all other document types (spreadsheets, database forms, database reports).

=== Text(-like) input form controls also support the "Vertical Alignment" property ===
Input form controls (text fields etc.) now also support the "Vertical Align" property known from non-input controls like fixed texts etc.

[[Image:Vert_alignment.png]]

== Report builder ==
=== Add Field dialog now accessible via keyboard ===
In the Report Designer the Add Field dialog can be accessed via the shortcut ALT+F8.

[[Image:Add_field.png]]

== Table design ==
=== New MetaData node for Database drivers to view column descriptions from the database ===
Now it is possible to define a new property in the drivers xcu file. Per default this is enabled for MySQL (JDBC) and Ado (including Access, Access only allows to view it, it can not be changed).

When this is enabled the table designer will display the column description, beside the former normal description which is used as help text. The column description is used has help text when the normal description is empty otherwise the normal description is used.

[[Image:Col_description.PNG]]
[[Category:Database]]

Documentation/DevGuide/Database/Extending Database Drivers

2010-02-10T11:49:46Z

Oj:

{{Documentation/DevGuide/DatabaseTOC
|Database2f=block
|ShowPrevNext=block
|PrevPage=Documentation/DevGuide/Database/Stored Procedures
|NextPage=Documentation/DevGuide/Database/Writing Database Drivers
}}
{{Documentation/DevGuideLanguages|Documentation/DevGuide/Database/{{SUBPAGENAME}}}}
{{DISPLAYTITLE:Extending Database Drivers}}
In the following section, extending existing SDBC drivers by [[Documentation/DevGuide/Extensions/Extensions | extensions]] is described.
These section is valid from since: OOo 3.3

Most drivers miss to support special features like to alter view definitions or to add or drop key of a table. Therefor these interfaces
* <idl>com.sun.star.sdb.tools.XViewAccess</idl>
* <idl>com.sun.star.sdb.tools.XTableRename</idl>
* <idl>com.sun.star.sdb.tools.XTableAlteration</idl>
* <idl>com.sun.star.sdb.tools.XKeyAlteration</idl>
* <idl>com.sun.star.sdb.tools.XIndexAlteration</idl>
can be implemented by an extension.

To enable the needed feature the extension has to extend the properties entry of the configuration of the driver. The configuration entry below the properties entry will be checked and if the service name can be instantiated it will be used to do the job. Below you'll see a table of mapping from configuration entry to service name.
{|border="1" cellpadding=4 style="border-collapse:collapse;"
|-bgcolor=#EDEDED
|Configuration name
|Interface name which has to to be implemented
|-
| ViewAccessServiceName
| <idl>com.sun.star.sdb.tools.XViewAccess</idl>
|-
| TableAlterationServiceName
| <idl>com.sun.star.sdb.tools.XTableAlteration</idl>
|-
| TableRenameServiceName
| <idl>com.sun.star.sdb.tools.XTableRename</idl>
|-
| IndexAlterationServiceName
| <idl>com.sun.star.sdb.tools.XIndexAlteration</idl>
|-
| KeyAlterationServiceName
| <idl>com.sun.star.sdb.tools.XKeyAlteration</idl>
|}

In favor to allow to get the definition of queries, forms and reports from other locations as the default file format specification, an extension may implement the <idl>com.sun.star.sdb.DocumentContainer</idl> service. The configuration entries are named
* Forms
* Reports
additionally to the interfaces defined in the service <idl>com.sun.star.sdb.DocumentContainer</idl> the interface <idl>com.sun.star.lang.XInitialization</idl> has to be implemented which will be called with a argument called "DatabaseDocument" containing the database document.

To allow to support command definitions from other locations, an extension may implement the <idl>com.sun.star.sdb.DefinitionContainer</idl> service. The configuration entry is named
* CommandDefinitions
A difference is that the interface <idl>com.sun.star.lang.XInitialization</idl> will be called with a "DataSource" argument.

The configuration fragment below shows how to define which service should be created to extend the view support and to extend the table alteration support.
<source lang="xml">
<oor:component-data oor:name="Drivers" oor:package="org.openoffice.Office.DataAccess" xmlns:oor="http://openoffice.org/2001/registry" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<node oor:name="Installed">
<node oor:name="jdbc:" oor:op="replace">
<prop oor:name="ParentURLPattern">
<value>jdbc:*</value>
</prop>
<prop oor:name="DriverTypeDisplayName" oor:type="xs:string">
<value xml:lang="en-US">SQL 2008 JDBC</value>
</prop>
<node oor:name="Properties">
<node oor:name="ViewAccessServiceName" oor:op="replace">
<prop oor:name="Value" oor:type="xs:string">
<value>com.sun.star.sdb.comp.SQL2008.ViewAccess</value>
</prop>
</node>
<node oor:name="TableAlterationServiceName" oor:op="replace">
<prop oor:name="Value" oor:type="xs:string">
<value>com.sun.star.sdb.comp.SQL2008.TableAlterService</value>
</prop>
</node>
</node>
</node>
</node>
</oor:component-data>
</source>

{{PDL1}}

[[Category:Documentation/Developer's Guide/Database Access]]

Documentation/DevGuide/Database/Writing Database Drivers

2010-02-09T10:04:30Z

Oj:

{{Documentation/DevGuide/DatabaseTOC
|Database2f=block
|ShowPrevNext=block
|PrevPage=Documentation/DevGuide/Database/Extending Database Drivers
|NextPage=Documentation/DevGuide/Database/SDBC Driver
}}
{{Documentation/DevGuideLanguages|Documentation/DevGuide/Database/{{SUBPAGENAME}}}}
{{DISPLAYTITLE:Writing Database Drivers}}
In the following sections, implementing an SDBC driver is described. The user should have some experience in the use of the SDBC API, or be familiar with the previous chapter about SDBC and SDBCX.

This section is divided into two parts. The first part describes the simple driver that includes only the SDBC layer with the PreparedStatements, Statements and ResultSets. The second part extends the simple driver from part one to a more sophisticated one. This driver provides access to Tables, Views, Groups, Users and others.

A skeleton for a C++ SDBC driver is provided in the samples folder. Some changes are necessary to create a working driver. Adjust the namespace and replace the word "skeleton" by a suitable driver name, and implement the necessary functions for the database.

An SDBC driver is simply the implementation of some SDBC services previously discussed.

{{PDL1}}

[[Category:Documentation/Developer's Guide/Database Access]]

Documentation/DevGuide/Database/Stored Procedures

2010-02-09T10:04:01Z

Oj:

{{Documentation/DevGuide/DatabaseTOC
|Database2e=block
|ShowPrevNext=block
|PrevPage=Documentation/DevGuide/Database/Using DBMS Features
|NextPage=Documentation/DevGuide/Database/Extending Database Drivers
}}
{{Documentation/DevGuideLanguages|Documentation/DevGuide/Database/{{SUBPAGENAME}}}}
{{DISPLAYTITLE:Stored Procedures}}

Stored procedures are server-side processes execute several SQL commands in a single step, and can be embedded in a server language for stored procedures with enhanced control capabilities. A procedure call usually has to be parameterized, and the results are result sets and additional out parameters. Stored procedures are handled by the method <code>prepareCall()</code> of the interface <idl>com.sun.star.sdbc.XConnection</idl>.

com::sun::star::sdbc::XPreparedStatement prepareCall( [in] string sql)

The method <code>prepareCall()</code> takes a an SQL statement that may contain one or more '<code>?</code>' in parameter placeholders. It returns a <idl>com.sun.star.sdbc.CallableStatement</idl>. A <code>CallableStatement</code> is a <idl>com.sun.star.sdbcx.PreparedStatement</idl> with two additional interfaces for out parameters:

<idl>com.sun.star.sdbc.XOutParameters</idl> is used to declare parameters as out parameters. All out parameters must be registered before a stored procedure is executed.

{|border="1" cellpadding=4 style="border-collapse:collapse;"
|-bgcolor=#EDEDED
!colspan="2"|Methods of <idl>com.sun.star.sdbc.XOutParameters</idl>
|-
|<idlm>com.sun.star.sdbc.XOutParameters:registerOutParameter</idlm>()
|Takes the arguments long parameterIndex, long sqlType, string typeName. Registers an output parameter and should be used for a user-named or REF output parameter. Examples of user-named types include: STRUCT, DISTINCT, OBJECT, and named array types.
|-
|<idlm>com.sun.star.sdbc.XOutParameters:registerNumericOutParameter</idlm>()
|Takes the arguments long parameterIndex, long sqlType, long scale. Registers an out parameter in the ordinal position parameterIndex with the <idl>com.sun.star.sdbc.DataType</idl> sqlType; scale is the number of digits on the right-hand side of the decimal point.
|}

The <idl>com.sun.star.sdbc.XRow</idl> is used to retrieve the values of out parameters. It consists of getXXX() methods and should be well-known from the common result sets.

{{PDL1}}

[[Category:Documentation/Developer's Guide/Database Access]]

Documentation/DevGuide/Database/Extending Database Drivers

2010-02-09T10:02:35Z

Oj:

{{Documentation/DevGuide/DatabaseTOC
|Database2f=block
|ShowPrevNext=block
|PrevPage=Documentation/DevGuide/Database/Stored Procedures
|NextPage=Documentation/DevGuide/Database/Writing Database Drivers
}}
{{Documentation/DevGuideLanguages|Documentation/DevGuide/Database/{{SUBPAGENAME}}}}
{{DISPLAYTITLE:Extending Database Drivers}}
In the following section, extending existing SDBC drivers by [[Documentation/DevGuide/Extensions/Extensions | extensions]] is described.
These section is valid from since: OOo 3.3

Most drivers miss to support special features like to alter view definitions or to add or drop key of a table. Therefor these interfaces
* <idl>com.sun.star.sdb.tools.XViewSupport</idl>
* <idl>com.sun.star.sdb.tools.XTableRename</idl>
* <idl>com.sun.star.sdb.tools.XTableAlteration</idl>
* <idl>com.sun.star.sdb.tools.XKeyAlteration</idl>
* <idl>com.sun.star.sdb.tools.XIndexAlteration</idl>
can be implemented by an extension.

To enable the needed feature the extension has to extend the properties entry of the configuration of the driver. The configuration entry below the properties entry will be checked and if the service name can be instantiated it will be used to do the job. Below you'll see a table of mapping from configuration entry to service name.
{|border="1" cellpadding=4 style="border-collapse:collapse;"
|-bgcolor=#EDEDED
|Configuration name
|Interface name which has to to be implemented
|-
| ViewSupportServiceName
| <idl>com.sun.star.sdb.tools.XViewSupport</idl>
|-
| TableAlterationServiceName
| <idl>com.sun.star.sdb.tools.XTableAlteration</idl>
|-
| TableRenameServiceName
| <idl>com.sun.star.sdb.tools.XTableRename</idl>
|-
| IndexAlterationServiceName
| <idl>com.sun.star.sdb.tools.XIndexAlteration</idl>
|-
| KeyAlterationServiceName
| <idl>com.sun.star.sdb.tools.XKeyAlteration</idl>
|}

In favor to allow to get the definition of queries, forms and reports from other locations as the default file format specification, an extension may implement a service which implement the following named interfaces. The configuration entries are named
* CommandDefinitionSupplier
* FormSupplier
* ReportSupplier
which all have to implement the interfaces
* <idl>com.sun.star.container.XNameAccess</idl>
* <idl>com.sun.star.container.XNameContainer</idl>
* <idl>com.sun.star.ucb.XContent</idl>
* <idl>com.sun.star.container.XChild</idl>
* <idl>com.sun.star.container.XContainer</idl>
* <idl>com.sun.star.container.XContainerApproveBroadcaster</idl>
* <idl>com.sun.star.lang.XInitialization</idl>

The configuration fragment below shows how to define which service should be created to extend the view support and to extend the table alteration support.
<source lang="xml">
<oor:component-data oor:name="Drivers" oor:package="org.openoffice.Office.DataAccess" xmlns:oor="http://openoffice.org/2001/registry" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<node oor:name="Installed">
<node oor:name="jdbc:" oor:op="replace">
<prop oor:name="ParentURLPattern">
<value>jdbc:*</value>
</prop>
<prop oor:name="DriverTypeDisplayName" oor:type="xs:string">
<value xml:lang="en-US">SQL 2008 JDBC</value>
</prop>
<node oor:name="Properties">
<node oor:name="ViewSupportServiceName" oor:op="replace">
<prop oor:name="Value" oor:type="xs:string">
<value>com.sun.star.sdb.comp.SQL2008.ViewSupport</value>
</prop>
</node>
<node oor:name="TableAlterationServiceName" oor:op="replace">
<prop oor:name="Value" oor:type="xs:string">
<value>com.sun.star.sdb.comp.SQL2008.TableAlterService</value>
</prop>
</node>
</node>
</node>
</node>
</oor:component-data>
</source>

{{PDL1}}

[[Category:Documentation/Developer's Guide/Database Access]]

HSQLDB Localization

2010-01-04T08:34:57Z

Oj:

In an effort to provide OpenOffice.org users with localized [[HSQLDB]] error messages (in the form [[HSQLDB Integration|shipped with OOo 2.0]], all error messages are English), a [http://dba.openoffice.org/servlets/ReadMsg?list=users&msgNo=3029 call was made] to the community to volunteer for translating the error messages from the [http://sourceforge.net/project/showfiles.php?group_id=23316&release_id=339171 HSQLDB source] into other languages.

So far, we have volunteers (V) and [[#Download|finished translations]] (F) for the following languages:

(The initial list was stolen from [http://qa.openoffice.org/issue_handling/submission_gateway.html#language here], feel free to add your own language/name if you want to participate.)

<pre>
(V) (F)
[ ] [ ] Basque
[X] [X] Brazilian(Pt): Olivier Hallot
[ ] [ ] Catalan
[ ] [ ] Chinese
[X] [X] Czech: Petr Kolesa
[ ] [ ] Danish
[ ] [ ] Finnish
[X] [X] French: Jérôme Paschoud
[X] [X] German: Thomas Kellerer
[ ] [ ] Greek
[ ] [ ] Hindi
[X] [X] Hungarian: Andras Timar
[X] [X] Japanese: foral
[X] [X] Korean: Jinwook Kim
[ ] [ ] Laotian
[ ] [ ] Malaysian
[ ] [ ] Netherlands
[ ] [ ] Norwegian
[ ] [ ] Polish
[ ] [ ] Portugese
[ ] [ ] Romanian
[ ] [ ] Russian
[ ] [ ] Serbian
[ ] [ ] Slovak
[X] [X] Slovenian: Vito Smolej
[ ] [ ] Spanish
[ ] [ ] Tamil
[ ] [ ] Thai
[ ] [ ] Turkish
[X] [ ] Vietnamese: Clytie Siddall
</pre>

== Encoding of the .properties files ==

The translated sql-error-messages_XX.properties files (XX stands for the language code) should be either in ISO-8859-1 or in plain ASCII with escaped unicode values. The native2ascii executable from Sun JDK can convert files to escaped unicode format. Other text editors on Windows known to handle escaped unicode: [http://www.ultraedit.com/ UltraEdit] 11.20 (shareware), [http://www.esperanto.mv.ru/UniRed/ENG/ UniRed] (freeware), [http://www.unipad.org/main/ SC Unipad] (shareware). There is also a command line tool called [http://billposer.org/Software/uni2ascii.html uni2ascii] which can do the job of converting unicode text files to escaped unicode text.

== Download ==

The current JAR file with the translated error messages can be found [http://dba.openoffice.org/files/documents/13/4302/hsqldb-l10n.jar at the DBA pages].
* download it to an arbitrary location
* in OOo, go to Tools|Options|OpenOffice.org|Java
* press the "Class Path" button
* add the JAR file you just downloaded to the class path
* close all dialogs with OK
* (re-start OpenOffice.org, if advised so)

== Translation Toolkit ==

Note that you can use prop2po.py from the [http://translate.sourceforge.net/ translate toolkit] to convert properties files to PO files. For example,

<pre>
prop2po.py -P sql-error-messages.properties -o po/sql-error-messages.pot
prop2po.py -t sql-error-messages.properties sql-error-messages_it.properties -o po/it.po
</pre>

this yield files like this:

<pre>
#: 001
msgid "08001 The database is already in use by another process"
msgstr "08001 L'archivio Ã¨ in uso da un altro processo"

#: 002
msgid "08003 Connection is closed"
msgstr "08003 Connessione chiusa"
</pre>

Samples from hsqldb 1.8 [http://davidf.sjsoft.com/files/hsqldb-po/ here]

[[Category:Localization]]
[[Category:HSQLDB]]

Uno/Spec/Log Environment

2009-06-23T10:17:29Z

Oj: New page: ==Feature== The Log purpose environment allows to log every UNO call to a defined component. The runtime environment variable UNO_ENV_LOG defines which components should be logged. The val...

==Feature==
The Log purpose environment allows to log every UNO call to a defined component. The runtime environment variable UNO_ENV_LOG defines which components should be logged. The value is a list of component names separated by semicolon (;). The log file must have been defined by the [http://tools.openoffice.org/profiling/profiling-howto.html RTL_LOGFILE] variable.

==API==
Specifying the to be logged components via environment variables.

For example:
<code>setenv "UNO_ENV_LOG" "com.sun.star.sdbcx.comp.hsqldb.Driver"</code>
<code>setenv "RTL_LOGFILE" "/tmp/log_test"</code>
The would trace all calls from the HsqlDB driver in OOo.

Runtime environment variable:
<code>"UNO_ENV_LOG"</code>
<code>"RTL_LOGFILE"</code>

==Dependencies==
* [[../Purpose Environment]]
* [[Uno/Spec/Environment Substitution]]

[[Category:Spec]]
[[Category:Uno]]
[[Category:Uno:Spec]]

SUN Report Builder

2009-05-06T12:02:08Z

Oj: /* Release Info */

== General Info ==

A new official name exists: SUN Report Builder. See issue 78437 
For more technical info, please read: [http://wiki.services.openoffice.org/wiki/SUN_Report_Builder Sun Report Builder] and [http://wiki.services.openoffice.org/wiki/SUN_Report_Builder:Planned_Features Planned Feature]

Download the [http://extensions.services.openoffice.org/project/reportdesign SUN Report Builder Extension]. The latest release is 1.0.6.

=== Release Info ===

* 1.1.0: formula editor and support of the ODF formula syntax
* 1.1.0: meta data support like author and title
* 1.1.0: support of charts
* 1.1.0: report wizard
* 1.0.6: report design loses its modification state when report is executed (93014)
* 1.0.6: chart in generated report displays wrong values (93735)
* 1.0.6: time values in generated reports are always displayed as if they were forenoon (93443)
* 1.0.6: Running a report is not possible (error) (95414)
* 1.0.5: Report Builder cannot be installed (93559)
* 1.0.4: The creation of reports with grouping is working again.

=== Roadmap ===

1.1 is expected to be released May 7th, 2009.

News about the report designer can be found on [http://blogs.sun.com/GullFOSS/tags/report GullFOSS].

The [[CWS]] page inside [[EIS]] can be found [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Foj14 here].

The [[Spec]] can be found [http://dba.openoffice.org/specifications/index.html here].

== Install Steps ==

* download the OOo 2.3 install set for your platform (at the moment only windows and linux is available)
* [optional] adjust the UserInstallation path in the program/bootstraprc or program/bootstrap.ini file
* start the office and open the extension manager (TOOLS/EXTENSION MANAGER)
* add the report designer extension
* open any database 
* use 'Create Report in DesignView ..' from the Report panel
=> the SUN Report Designer should appear

== Taskhandling inside this CWS ==

''Attention: the CWS is already integrated and some info get redundant''

Before writing a new Issue, please check if it not already exists: [http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&component=Database+access&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=RPT&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=new_implementation&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query RPT Double Check]

New Issue should contain:
* summary should start with 'RPT: '
* set keyword 'new_implementation'
* default prio (prio 3)
* default owner: OJ
* no target (this is the default for new issues, so don't care for the moment)
* "Version" should be the version you're testing f.e. "RPT 1.0.0"
[http://www.openoffice.org/issues/enter_bug.cgi?component=Database%20access&version=RPT%200%2E4%2E0%2E20070612&assigned_to=oj&short_desc=RPT: one-click submission]

If a task inside this cws has the target "2.3" it's a showstopper. Without a fix for this issue we can't release a final version. All issue with this target should fixed until 5.July 2007. ([http://wiki.services.openoffice.org/wiki/OOoRelease23 Feature Freeze])

A target "2.x" means that this issue should be fixed for the final release. However we can live with the issue for a first final release. This issue should then be fixed inthe first update.

Target "not determined" meas that this is an issue which should be fixed in the near future.

If an issue has no target "---" then the report designer i-Team has not yet decide what to do with this issue.

Further Info list for testable features: [http://wiki.services.openoffice.org/wiki/Feature_Freeze_Testing_2.3#Component_:_dba_-_Database Feature Freeze Testing 2.3]

== Autor ==

[mailto:Marc.Neumann@Sun.com?subject:OOoWiki Marc Neumann] [mailto:Christoph.Lukasiak@Sun.com?subject:OOoWiki Christoph Lukasiak] ([http://wiki.services.openoffice.org/wiki/User:Clu Clu]) 1 June 2007 
''Please do not change the logical content of this site without
acknowledge of the author, the [http://wiki.services.openoffice.org/wiki/Database_Docu_Coordinator Database Docu Coordinator] or the [http://wiki.services.openoffice.org/wiki/Project_Lead OOo QA Project Lead/Co-Leads].''

[[Category:Quality Assurance]]
[[Category:Sun Report Builder]]

SUN Report Builder/Planned Features

2009-05-06T12:00:59Z

Oj: /* Report Wizard */

Download the '''Sun Report Builder''' [http://extensions.services.openoffice.org/project/reportdesign here].
The following list describes all features which could be implemented for the OOo 3.x time frame.

==Planned Features==
As every time any kind of help is very appreciated.
===First Priority===
#[[#Sub Reports|Sub Reports]]

===Second Priority===
#[[#Add-On functionality|Add-On functionality]]
#[[#Formula API|Formula API]]
#[[#AutoFormating of Controls|AutoFormating of Controls]]
#[[#Repeatable Group Footer|Repeatable Group Footer]]
#[[#Hyperlink Controls|Hyperlink Controls]]
#[[#Scripting Support|Scripting Support]]
#[[#Multi Column Support|Multi Column Support]]
#[[#Flowing Text in Sections|Flowing Text in Sections]]

==Sub Reports==
Allow to insert reports into reports like it is possible to insert forms in forms.
==Add-On functionality==
Define an API which can be used by external developers to provide additional functionality to Sun Report Builder e.g. barcodes.
==Meta Data for Reports==
Export meta data like
* Who designed the report
* Who executed the report
* When was it last time printed
* Any other information about the report itself
==Formula API==
Definition of a general approach to declare functions and formulas. This should allow external developers to define new functions and formulas which can be used in a report.
==AutoFormatting of Controls==
Assign styles to controls like it possible to assign styles at paragraphs in Writer.
==Repeatable Group Footer==
Allow that group footer will be printed on each side even when the group doesn't change.
==Hyperlink Controls==
Create a new control which will create a hyper link in the resulting report. Either hard coded or filled by a column value.
==Scripting Support==
Event driven JAVA scripting when report will be executed.

==Multi Column Support==
Allow to create a report which uses multiple columns to print.
==Flowing Text in Sections==
Currently the design in resulting report is based on tables which have fixed height and width. This will change when using flowing text. This would also allow the user to write any text in a section and to insert some kinds of reporting elements which behave like field commands.

[[Category:Sun Report Builder]]
[[Category:Feature]]

SUN Report Builder/Planned Features

2009-05-06T12:00:42Z

Oj: /* Formula Editor */

Download the '''Sun Report Builder''' [http://extensions.services.openoffice.org/project/reportdesign here].
The following list describes all features which could be implemented for the OOo 3.x time frame.

==Planned Features==
As every time any kind of help is very appreciated.
===First Priority===
#[[#Sub Reports|Sub Reports]]

===Second Priority===
#[[#Add-On functionality|Add-On functionality]]
#[[#Formula API|Formula API]]
#[[#AutoFormating of Controls|AutoFormating of Controls]]
#[[#Repeatable Group Footer|Repeatable Group Footer]]
#[[#Hyperlink Controls|Hyperlink Controls]]
#[[#Scripting Support|Scripting Support]]
#[[#Multi Column Support|Multi Column Support]]
#[[#Flowing Text in Sections|Flowing Text in Sections]]

==Report Wizard==
Creation of a new report wizard which uses the new format (file and API) as the [[SUN_Report_Builder]] does.

==Sub Reports==
Allow to insert reports into reports like it is possible to insert forms in forms.
==Add-On functionality==
Define an API which can be used by external developers to provide additional functionality to Sun Report Builder e.g. barcodes.
==Meta Data for Reports==
Export meta data like
* Who designed the report
* Who executed the report
* When was it last time printed
* Any other information about the report itself
==Formula API==
Definition of a general approach to declare functions and formulas. This should allow external developers to define new functions and formulas which can be used in a report.
==AutoFormatting of Controls==
Assign styles to controls like it possible to assign styles at paragraphs in Writer.
==Repeatable Group Footer==
Allow that group footer will be printed on each side even when the group doesn't change.
==Hyperlink Controls==
Create a new control which will create a hyper link in the resulting report. Either hard coded or filled by a column value.
==Scripting Support==
Event driven JAVA scripting when report will be executed.

==Multi Column Support==
Allow to create a report which uses multiple columns to print.
==Flowing Text in Sections==
Currently the design in resulting report is based on tables which have fixed height and width. This will change when using flowing text. This would also allow the user to write any text in a section and to insert some kinds of reporting elements which behave like field commands.

[[Category:Sun Report Builder]]
[[Category:Feature]]

SUN Report Builder/Planned Features

2009-05-06T12:00:21Z

Oj: /* Second Priority */

Download the '''Sun Report Builder''' [http://extensions.services.openoffice.org/project/reportdesign here].
The following list describes all features which could be implemented for the OOo 3.x time frame.

==Planned Features==
As every time any kind of help is very appreciated.
===First Priority===
#[[#Sub Reports|Sub Reports]]

===Second Priority===
#[[#Add-On functionality|Add-On functionality]]
#[[#Formula API|Formula API]]
#[[#AutoFormating of Controls|AutoFormating of Controls]]
#[[#Repeatable Group Footer|Repeatable Group Footer]]
#[[#Hyperlink Controls|Hyperlink Controls]]
#[[#Scripting Support|Scripting Support]]
#[[#Multi Column Support|Multi Column Support]]
#[[#Flowing Text in Sections|Flowing Text in Sections]]

==Report Wizard==
Creation of a new report wizard which uses the new format (file and API) as the [[SUN_Report_Builder]] does.

==Sub Reports==
Allow to insert reports into reports like it is possible to insert forms in forms.
==Add-On functionality==
Define an API which can be used by external developers to provide additional functionality to Sun Report Builder e.g. barcodes.
==Meta Data for Reports==
Export meta data like
* Who designed the report
* Who executed the report
* When was it last time printed
* Any other information about the report itself
==Formula API==
Definition of a general approach to declare functions and formulas. This should allow external developers to define new functions and formulas which can be used in a report.
==AutoFormatting of Controls==
Assign styles to controls like it possible to assign styles at paragraphs in Writer.
==Repeatable Group Footer==
Allow that group footer will be printed on each side even when the group doesn't change.
==Hyperlink Controls==
Create a new control which will create a hyper link in the resulting report. Either hard coded or filled by a column value.
==Scripting Support==
Event driven JAVA scripting when report will be executed.
==Formula Editor==
Allow to define a formula by UI like Calc support it.
==Multi Column Support==
Allow to create a report which uses multiple columns to print.
==Flowing Text in Sections==
Currently the design in resulting report is based on tables which have fixed height and width. This will change when using flowing text. This would also allow the user to write any text in a section and to insert some kinds of reporting elements which behave like field commands.

[[Category:Sun Report Builder]]
[[Category:Feature]]

SUN Report Builder/Planned Features

2009-05-06T11:59:14Z

Oj: /* Chart */

Download the '''Sun Report Builder''' [http://extensions.services.openoffice.org/project/reportdesign here].
The following list describes all features which could be implemented for the OOo 3.x time frame.

==Planned Features==
As every time any kind of help is very appreciated.
===First Priority===
#[[#Sub Reports|Sub Reports]]

===Second Priority===
#[[#Add-On functionality|Add-On functionality]]
#[[#AutoFormating of Controls|AutoFormating of Controls]]
#[[#Repeatable Group Footer|Repeatable Group Footer]]
#[[#Hyperlink Controls|Hyperlink Controls]]
#[[#Scripting Support|Scripting Support]]
#[[#Multi Column Support|Multi Column Support]]
#[[#Flowing Text in Sections|Flowing Text in Sections]]

==Report Wizard==
Creation of a new report wizard which uses the new format (file and API) as the [[SUN_Report_Builder]] does.

==Sub Reports==
Allow to insert reports into reports like it is possible to insert forms in forms.
==Add-On functionality==
Define an API which can be used by external developers to provide additional functionality to Sun Report Builder e.g. barcodes.
==Meta Data for Reports==
Export meta data like
* Who designed the report
* Who executed the report
* When was it last time printed
* Any other information about the report itself
==Formula API==
Definition of a general approach to declare functions and formulas. This should allow external developers to define new functions and formulas which can be used in a report.
==AutoFormatting of Controls==
Assign styles to controls like it possible to assign styles at paragraphs in Writer.
==Repeatable Group Footer==
Allow that group footer will be printed on each side even when the group doesn't change.
==Hyperlink Controls==
Create a new control which will create a hyper link in the resulting report. Either hard coded or filled by a column value.
==Scripting Support==
Event driven JAVA scripting when report will be executed.
==Formula Editor==
Allow to define a formula by UI like Calc support it.
==Multi Column Support==
Allow to create a report which uses multiple columns to print.
==Flowing Text in Sections==
Currently the design in resulting report is based on tables which have fixed height and width. This will change when using flowing text. This would also allow the user to write any text in a section and to insert some kinds of reporting elements which behave like field commands.

[[Category:Sun Report Builder]]
[[Category:Feature]]

SUN Report Builder/Planned Features

2009-05-06T11:58:58Z

Oj: /* Second Priority */

Download the '''Sun Report Builder''' [http://extensions.services.openoffice.org/project/reportdesign here].
The following list describes all features which could be implemented for the OOo 3.x time frame.

==Planned Features==
As every time any kind of help is very appreciated.
===First Priority===
#[[#Sub Reports|Sub Reports]]

===Second Priority===
#[[#Add-On functionality|Add-On functionality]]
#[[#AutoFormating of Controls|AutoFormating of Controls]]
#[[#Repeatable Group Footer|Repeatable Group Footer]]
#[[#Hyperlink Controls|Hyperlink Controls]]
#[[#Scripting Support|Scripting Support]]
#[[#Multi Column Support|Multi Column Support]]
#[[#Flowing Text in Sections|Flowing Text in Sections]]

==Report Wizard==
Creation of a new report wizard which uses the new format (file and API) as the [[SUN_Report_Builder]] does.

==Chart==
Allow to insert charts into reports.
==Sub Reports==
Allow to insert reports into reports like it is possible to insert forms in forms.
==Add-On functionality==
Define an API which can be used by external developers to provide additional functionality to Sun Report Builder e.g. barcodes.
==Meta Data for Reports==
Export meta data like
* Who designed the report
* Who executed the report
* When was it last time printed
* Any other information about the report itself
==Formula API==
Definition of a general approach to declare functions and formulas. This should allow external developers to define new functions and formulas which can be used in a report.
==AutoFormatting of Controls==
Assign styles to controls like it possible to assign styles at paragraphs in Writer.
==Repeatable Group Footer==
Allow that group footer will be printed on each side even when the group doesn't change.
==Hyperlink Controls==
Create a new control which will create a hyper link in the resulting report. Either hard coded or filled by a column value.
==Scripting Support==
Event driven JAVA scripting when report will be executed.
==Formula Editor==
Allow to define a formula by UI like Calc support it.
==Multi Column Support==
Allow to create a report which uses multiple columns to print.
==Flowing Text in Sections==
Currently the design in resulting report is based on tables which have fixed height and width. This will change when using flowing text. This would also allow the user to write any text in a section and to insert some kinds of reporting elements which behave like field commands.

[[Category:Sun Report Builder]]
[[Category:Feature]]

SUN Report Builder/Planned Features

2009-05-06T11:57:46Z

Oj: /* First Priority */

Download the '''Sun Report Builder''' [http://extensions.services.openoffice.org/project/reportdesign here].
The following list describes all features which could be implemented for the OOo 3.x time frame.

==Planned Features==
As every time any kind of help is very appreciated.
===First Priority===
#[[#Sub Reports|Sub Reports]]

===Second Priority===
#[[#Add-On functionality|Add-On functionality]]
#[[#Meta Data for reports|Meta Data for reports]]
#[[#Formula API|Formula API]]
#[[#AutoFormating of Controls|AutoFormating of Controls]]
#[[#Repeatable Group Footer|Repeatable Group Footer]]
#[[#Hyperlink Controls|Hyperlink Controls]]
#[[#Scripting Support|Scripting Support]]
#[[#Formula Editor|Formula Editor]]
#[[#Multi Column Support|Multi Column Support]]
#[[#Flowing Text in Sections|Flowing Text in Sections]]

==Report Wizard==
Creation of a new report wizard which uses the new format (file and API) as the [[SUN_Report_Builder]] does.

==Chart==
Allow to insert charts into reports.
==Sub Reports==
Allow to insert reports into reports like it is possible to insert forms in forms.
==Add-On functionality==
Define an API which can be used by external developers to provide additional functionality to Sun Report Builder e.g. barcodes.
==Meta Data for Reports==
Export meta data like
* Who designed the report
* Who executed the report
* When was it last time printed
* Any other information about the report itself
==Formula API==
Definition of a general approach to declare functions and formulas. This should allow external developers to define new functions and formulas which can be used in a report.
==AutoFormatting of Controls==
Assign styles to controls like it possible to assign styles at paragraphs in Writer.
==Repeatable Group Footer==
Allow that group footer will be printed on each side even when the group doesn't change.
==Hyperlink Controls==
Create a new control which will create a hyper link in the resulting report. Either hard coded or filled by a column value.
==Scripting Support==
Event driven JAVA scripting when report will be executed.
==Formula Editor==
Allow to define a formula by UI like Calc support it.
==Multi Column Support==
Allow to create a report which uses multiple columns to print.
==Flowing Text in Sections==
Currently the design in resulting report is based on tables which have fixed height and width. This will change when using flowing text. This would also allow the user to write any text in a section and to insert some kinds of reporting elements which behave like field commands.

[[Category:Sun Report Builder]]
[[Category:Feature]]

API/Samples/Java/Database/TableStructure(SDBCX)

2009-04-08T06:33:48Z

Oj: New page: == Table Structure (extended) == Beside the database meta data interface, the interfaces in the namespace com.sun.star.sdbcx.* supports a different more objective orientated way on looking...

== Table Structure (extended) ==
Beside the database meta data interface, the interfaces in the namespace com.sun.star.sdbcx.* supports a different more objective orientated way on looking at the database.

<source lang="java">
public void displayTableProperties() throws com.sun.star.uno.Exception
{
// the variable xTabSup is a XTablesSupplier which you get from the XDriver in conjunction with the connection
XNameAccess xTables = xTabSup.getTables();
String[] aTableNames = xTables.getElementNames();
if ( 0 != aTableNames.length )
{
Object table = xTables.getByName(aTableNames[0]);
XPropertySet xProp = (XPropertySet) UnoRuntime.queryInterface(XPropertySet.class, table);
System.out.println("Name: " + xProp.getPropertyValue(NAME));
System.out.println("CatalogName: " + xProp.getPropertyValue("CatalogName"));
System.out.println("SchemaName: " + xProp.getPropertyValue("SchemaName"));
System.out.println("Description: " + xProp.getPropertyValue("Description"));
// the following property is optional so we first must check if it exists
if ( xProp.getPropertySetInfo().hasPropertyByName(TYPE) )
{
System.out.println("Type: " + xProp.getPropertyValue(TYPE));
}
System.out.println("Columns:");
XColumnsSupplier columnsSupplier = (XColumnsSupplier) UnoRuntime.queryInterface(XColumnsSupplier.class, table);
printColumns(columnsSupplier);
System.out.println("Keys:");
printKeys(columnsSupplier);
}
}
//###########################################################
// 15. example
// print all columns of a XColumnsSupplier
//###########################################################
public static void printColumns(final XColumnsSupplier xColumnsSup) throws com.sun.star.uno.Exception, SQLException
{
System.out.println("Example printColumns");
// the table must be at least support a XColumnsSupplier interface
System.out.println("--- Columns ---");
XNameAccess xColumns = xColumnsSup.getColumns();
String[] aColumnNames = xColumns.getElementNames();
for ( int i = 0; i <= aColumnNames.length - 1; i++ )
{
System.out.println(" " + aColumnNames[i]);
}
}
//###########################################################
// 16. example
// print all keys inclusive the columns of a key
//###########################################################

public static void printKeys(final XColumnsSupplier xColumnsSup) throws com.sun.star.uno.Exception, SQLException
{
System.out.println("Example printKeys");
XKeysSupplier xKeysSup = (XKeysSupplier) UnoRuntime.queryInterface(XKeysSupplier.class, xColumnsSup);
if ( xKeysSup != null )
{
System.out.println("--- Keys ---");
XIndexAccess xKeys = xKeysSup.getKeys();
for ( int i = 0; i < xKeys.getCount(); i++ )
{
Object key = xKeys.getByIndex(i);
XPropertySet xProp = (XPropertySet) UnoRuntime.queryInterface(XPropertySet.class, key);
System.out.println(" " + xProp.getPropertyValue(NAME));
XColumnsSupplier xKeyColumnsSup = (XColumnsSupplier) UnoRuntime.queryInterface(XColumnsSupplier.class, xProp);
printColumns(xKeyColumnsSup);
}
}
}
</source>

API/Samples/Java/Database/TableStructure

2009-04-08T06:21:22Z

Oj: New page: == Table Structure == The database meta data interface gives you access to many information about the structure of the database. The example below show how to display all tables of the dat...

== Table Structure ==
The database meta data interface gives you access to many information about the structure of the database. The example below show how to display all tables of the database including the column namess.

<source lang="java">
// displays the structure of the first table
public static void displayTableStructure(final XConnection con) throws com.sun.star.uno.Exception
{
XDatabaseMetaData dm = con.getMetaData();
XResultSet rsTables = dm.getTables(null, "%", "SALES", null);
XRow rowTB = (XRow) UnoRuntime.queryInterface(XRow.class, rsTables);
while ( rsTables.next() )
{
String catalog = rowTB.getString(1);
if ( rowTB.wasNull() )
{
catalog = null;
}

String schema = rowTB.getString(2);
if ( rowTB.wasNull() )
{
schema = null;
}

String table = rowTB.getString(3);
String type = rowTB.getString(4);
System.out.println("Catalog: " + catalog + " Schema: " + schema + " Table: " + table + " Type: " + type);
System.out.println("------------------ Columns ------------------");
XResultSet rsColumns = dm.getColumns(catalog, schema, table, "%");
XRow rowCL = (XRow) UnoRuntime.queryInterface(XRow.class, rsColumns);
while ( rsColumns.next() )
{
System.out.println("Column: " + rowCL.getString(4) + " Type: " + rowCL.getInt(5) + " TypeName: " + rowCL.getString(6));
}

}
}
</source>

File:Base TestCase 6.gif

2009-02-25T11:48:10Z

Oj: uploaded a new version of "Image:Base TestCase 6.gif"

File:Base TestCase 5.gif

2009-02-25T11:47:52Z

Oj: uploaded a new version of "Image:Base TestCase 5.gif"

File:Base TestCase 4.gif

2009-02-25T11:47:32Z

Oj: uploaded a new version of "Image:Base TestCase 4.gif"

File:Base TestCase 3.gif

2009-02-25T11:47:01Z

Oj: uploaded a new version of "Image:Base TestCase 3.gif"

File:Base TestCase 2.gif

2009-02-25T11:46:46Z

Oj: uploaded a new version of "Image:Base TestCase 2.gif"

File:Base TestCase 1.gif

2009-02-25T11:46:10Z

Oj: uploaded a new version of "Image:Base TestCase 1.gif"

File:Base TestCase 6.gif

2009-02-25T11:42:28Z

Oj: uploaded a new version of "Image:Base TestCase 6.gif"

Base/Performance

2009-02-25T11:01:24Z

Oj: /* Test Results */

= Performance =
This page contains all thought and ideas we have around performance.

== General ==
At the moment, this is just a basket to hold items I needed to remove from other pages. On the medium term, this is to be the central entry point for performance considerations in Base.

* opening forms
* starting the Java-based wizards
* creating a new HSQLDB (which implies starting the JVM)
* saving a form
* flickering when starting the New Database wizard from within the start center

== Row Fetching ==
We currently evaluate how row fetching can be accelerated. Fetching thousands of rows isn't as fast as it could be.
=== Test Cases ===
{| class="wikitable"
|-
! Nr || Test Case !! Source Database !! Destination Database
|-
| 1.
| Jump to last row (65514 rows x 21 columns)
| Flat (csv)
| Flat (csv)
|-
| 2.
| Jump to last row (20000 rows x 11 columns)
| MySQL (JDBC)
| MySQL (JDBC)
|-
| 3.
| Open a spreadsheet file with one table (65514 rows x 21 columns)
| Spreadsheet
| Spreadsheet
|-
| 4.
| Jump to last row (65514 rows x 21 columns)
| Spreadsheet
| Spreadsheet
|-
| 5.
| Copy a table (13000 rows x 19 columns)
| HsqlDB (native)
| HsqlDB (native)
|-
| 6.
| Copy a table (13000 rows x 19 columns)
| Spreadsheet
| HsqlDB (native)
|}
=== Test Results ===
All test results are normalized to 100% which is the worst case.
First results which could be achieved so far (less is better):
* Test Case 1
[[Image:Base_TestCase_1.gif]]
* Test Case 2
[[Image:Base_TestCase_2.gif]]
* Test Case 3
[[Image:Base_TestCase_3.gif]]
* Test Case 4
[[Image:Base_TestCase_4.gif]]
* Test Case 5
[[Image:Base_TestCase_5.gif]]
* Test Case 6
[[Image:Base_TestCase_6.gif]]

[[Category:Performance]]

Base/Performance

2009-02-25T10:59:37Z

Oj: /* Test Cases */

= Performance =
This page contains all thought and ideas we have around performance.

== General ==
At the moment, this is just a basket to hold items I needed to remove from other pages. On the medium term, this is to be the central entry point for performance considerations in Base.

* opening forms
* starting the Java-based wizards
* creating a new HSQLDB (which implies starting the JVM)
* saving a form
* flickering when starting the New Database wizard from within the start center

== Row Fetching ==
We currently evaluate how row fetching can be accelerated. Fetching thousands of rows isn't as fast as it could be.
=== Test Cases ===
{| class="wikitable"
|-
! Nr || Test Case !! Source Database !! Destination Database
|-
| 1.
| Jump to last row (65514 rows x 21 columns)
| Flat (csv)
| Flat (csv)
|-
| 2.
| Jump to last row (20000 rows x 11 columns)
| MySQL (JDBC)
| MySQL (JDBC)
|-
| 3.
| Open a spreadsheet file with one table (65514 rows x 21 columns)
| Spreadsheet
| Spreadsheet
|-
| 4.
| Jump to last row (65514 rows x 21 columns)
| Spreadsheet
| Spreadsheet
|-
| 5.
| Copy a table (13000 rows x 19 columns)
| HsqlDB (native)
| HsqlDB (native)
|-
| 6.
| Copy a table (13000 rows x 19 columns)
| Spreadsheet
| HsqlDB (native)
|}
=== Test Results ===
First results which could be achieved so far (less is better):
* Test Case 1
[[Image:Base_TestCase_1.gif]]
* Test Case 2
[[Image:Base_TestCase_2.gif]]
* Test Case 3
[[Image:Base_TestCase_3.gif]]
* Test Case 4
[[Image:Base_TestCase_4.gif]]
* Test Case 5
[[Image:Base_TestCase_5.gif]]
* Test Case 6
[[Image:Base_TestCase_6.gif]]

[[Category:Performance]]

File:Base TestCase 6.gif

2009-02-25T10:58:40Z

Oj:

File:Base TestCase 4.gif

2009-02-25T10:58:10Z

Oj:

File:Base TestCase 3.gif

2009-02-25T10:39:46Z

Oj:

File:Base TestCase 1.gif

2009-02-25T10:39:07Z

Oj:

File:Base TestCase 2.gif

2009-02-25T10:37:35Z

Oj:

File:Base TestCase 5.gif

2009-02-25T10:32:46Z

Oj:

Base/Performance

2009-02-25T09:46:20Z

Oj: /* Row Fetching */

= Performance =
This page contains all thought and ideas we have around performance.

== General ==
At the moment, this is just a basket to hold items I needed to remove from other pages. On the medium term, this is to be the central entry point for performance considerations in Base.

* opening forms
* starting the Java-based wizards
* creating a new HSQLDB (which implies starting the JVM)
* saving a form
* flickering when starting the New Database wizard from within the start center

== Row Fetching ==
We currently evaluate how row fetching can be accelerated. Fetching thousands of rows isn't as fast as it could be.
=== Test Cases ===
{| class="wikitable"
|-
! Test Case !! Source Database !! Destination Database
|-
| Jump to last row (65514 rows x 21 columns)
| Flat (csv)
| Flat (csv)
|-
| Jump to last row (20000 rows x 11 columns)
| MySQL (JDBC)
| MySQL (JDBC)
|-
| Open a spreadsheet file with one table (65514 rows x 21 columns)
| Spreadsheet
| Spreadsheet
|-
| Jump to last row (65514 rows x 21 columns)
| Spreadsheet
| Spreadsheet
|-
| Copy a table (13000 rows x 19 columns)
| HsqlDB (native)
| HsqlDB (native)
|-
| Copy a table (13000 rows x 19 columns)
| Spreadsheet
| HsqlDB (native)
|}
[[Category:Performance]]

Base/Performance

2009-02-25T09:23:37Z

Oj:

Database

2009-02-25T09:22:53Z

Oj: /* English */

{{Database/Lang|Database}}
This page is hosted by the [http://wiki.services.openoffice.org/wiki/Database_Docu_Coordinator OOo Database Docu Coordinator], who are members of the [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team].
You can find here links to Base documentation ordered by languages and topics. Feel free to add documents, you are missing, to this list.

Resources related to OpenOffice.org Base:

= English =
The following links are in English.
== Manuals ==
=== General ===
* Base
: [[Documentation/Database | Database]]
: Description of the features of OpenOffice.org Base (short overview), Documentation resources and official sites

* OpenOffice.org User Guides (Getting started with Base) - ''PDF''
: [http://documentation.openoffice.org/manuals/oooauthors2/0110GS-GettingStartedWithBase.pdf Getting started with Base]
: Learn how to create a database, queries, forms and reports and connect to and use other data sources within OOo-Base.

* OpenOffice.org Base Manual
: [http://nothickmanuals.info/doku.php/articles:ooobaseprimer OpenOffice.org Base Primer]
: Initial Authors: Andrew 'Drew' Jensen, Frank Schoenheit, et al.
: A short screenshot-guided overview on how to use Base.

* Mid Level Base Tutorial
: [http://documentation.openoffice.org/servlets/ProjectDocumentList?folderID=778&expandFolder=778&folderID=597 Mid Level Base Tutorial]
: Innitial Authors: Mariano Casanova, Andrew 'Drew' Jensen

* Beginners - Example Database - Base Tutorial
: [http://www.oooforum.org/forum/viewtopic.phtml?t=25060 Example]
: Initial author: Andrew 'Drew' Jensen
: This tutorial covers creating a first database using OOoBase. It is intended for those that have not used Base before or those that have never used any database manager.

* Base and Macros
: [http://www.pitonyak.org/database/ Pitonyak's document]
: Initial author: Andrew Pitonyak
: This documentation focuses on operating a database with the help of OpenOffice.org Macros.

* Database: "ooBase", aka "Base"
: [http://sheepdogguides.com/fdb/fdb1main.htm Base Tutorial by Sheepdogguides.com]
: Initial author: TK Boyd
: After a short introduction some every day tasks like importing data from other tables are explained.

* Bringing data into OpenOffice 2.0's database
: [http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1222186,00.html Database]
: Initial author: Solveig Haugland
: Screenshot guided tutorial on how to import data into Openoffice.org Base.

* New Features in 3.1
: [[Base/New_features_in_3_1|New Features]]
: Initial author: Reizinger Zoltan
: Compiled from mailing list

=== Tables ===

* [[Standard Distributed Schema]]

=== Queries ===
* [[Built-in functions and Stored Procedures]]

=== Reports ===
* [[SUN Report Builder]]
: ''description followed''

* Sun Report Builder (Reference)
: [http://wiki.pentaho.com/display/Reporting/Pentaho+Reporting+Community+Documentation Reference]
: ''description follow ''

* Sun Report Builder Documentation
: [[SUN_Report_Builder/Documentation|Documentation]]
: Basic Features

* Functions in Reports
: [http://wiki.pentaho.com/display/Reporting/08.+Functions+and+Expressions Functions and Expressions]
: ''description follow - Not available now''

* Functions in Reports
: [[SUN Report Builder/Functions]]
: ''description followed''

=== Developer ===
* Working basis to make the user guide better
: [[Documentation/OOoAuthors_User_Manual/Getting_Started/Getting_Started_with_Base | Getting_Started/Getting_Started_with_Base]]
: ''description followed''

* Using Macros in Database Files
: [[Macros_in_Database_Documents | Macros_in_Database_Documents]]
: 'Specification to develope this functionality

=== FAQ ===
* Common tasks
: [[Common_tasks | Common_tasks]]
: Initial author: Andrew 'Drew' Jensen
: Many good questions, no answers.

=== Misc ===
* HSQLDB Tips and Tricks
: [[HSQLDB:Tips_and_Tricks | Tips_and_Tricks]]
: ''description followed''

* [http://nothickmanuals.info/doku.php/articles:ooobaseprimer http://nothickmanuals.info/doku.php/articles:ooobaseprimer]

* [http://www.baseusers.com/index.html http://www.baseusers.com/index.html]

== Connecting ==
* Base New Driver Tutorial
: [[Base_New_Driver_Tutorial]]
: Initial author: Robert Vojta
: This small How-To contains a simple step-by-step introduction on how to put your driver inside the connectivity module. The second part of this document covers differences between a driver in connectivity module and a driver in an UNO package.

* Better Database Drivers
: [[BetterDatabaseDrivers]]
: Initial author:Eric Bischoff
:Some ideas for a better and simpler infrastructure for database drivers

* Connecting to Microsoft Access
: [[Connecting_to_Microsoft_Access]]
: Initial author: Regina Henschel
: These article describes how to connect to a Microsoft Access database file, if you use a MS Windows operating system.

* OpenOffice.org Base - Database Drivers
: [http://dba.openoffice.org/drivers/ http://dba.openoffice.org/drivers/]

* Connecting with MySQL
: [[Connect_MySQLandBase]]

* An overview page
: Native PostgreSQL Driver
: [http://dba.openoffice.org/drivers/postgresql/index.html http://dba.openoffice.org/drivers/postgresql/index.html]

* SQL-lite Driver
: http://dba.openoffice.org/drivers/sqlite/index.html

* mdb-sdbc-driver-0.1.0
: [http://dba.openoffice.org/drivers/mdb/index.html http://dba.openoffice.org/drivers/mdb/index.html]
: Initial author: Wind Li (yl146652 [at] openoffice [dot] org)
: It is a try to connect a Linux system to MS Access. There is no further development.

* A working page
: [[MDB_Driver_Integration]]

* MSA-Base Faq
: [[MSA-Base_Faq]]

* Firebird driver update for OO.org
: [http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=config:oobase Jaybird OpenOffice.org Base support]

== Examples ==
=== General ===
* Base Example (Overview)
: [[Category:Base_Example]]
: Initial author: Frank Schönheit

* Standard Distributed Schema
: [[Standard_Distributed_Schema]]

=== Concrete Examples ===
* A club membership database
: [[A_club_membership_database]]
: Initial author: Andrew 'Drew' Jensen
: Description of creating an example database

* OpenOffice.org API - Code snippets
: [http://codesnippets.services.openoffice.org/Database/index.xml http://codesnippets.services.openoffice.org/Database/index.xml]
: Useful code snippets solving frequently asked questions.

* Base Example
: [[Help_Files]]

== Misc ==

* [http://user.services.openoffice.org/en/forum/viewforum.php?f=13 OOo Community Forum]
: Initial author: Andrew 'Drew' Jensen
: Starting Point for all kind of OOo Database Questions

== Testing ==

* Main Point of OOo Database Testing
: [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team Site]
: Initial Author: [[User:Clu Christoph Lukasiak]]

* Main Starter Document for QA Newbies
: [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html OOo QA How to Start Document]
: Initial Author: [[User:Wg Wolfram Garten]]

* [[Database_Automatic_Testing]]
* [[Documentation/OOoAuthors_User_Manual/Base_Guide/Planning |Base_Guide-Planning]]
* [[FAQ_%28Base%29 |FAQ Base]]
* [[OOoHelpOutline#Base_and_Database Base_and_Database]]

* [http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm]
: Connecting OpenOffice.org To A Remote MySQL Database] (event. 1.x)

= French =

The following Links are showing French documents. If someone translate them we can show here the correponding links.

= German =

The following Links are showing German documents. If someone translate them we can show here the correponding links.

* [[DE/Beispielsdatenbank_mit_Base]]

* http://dannenhoefer.de/faqstarbasic/Datenbanken.html

* http://de.openoffice.org/doc/howto_2_0/index.html#datenquellen_2_0

* [[DE/FAQ/Base]]

* End user documentation
: http://www.ooowiki.de/KategorieBase

= Portugese =

The following Links are showing Portugese documents. If someone translate them we can show here the correponding links.

http://broffice.org/files/Introdu%C3%A7%C3%A3o_ao%20BrOffice.org_Base_2.0.x.odt

=Copyright=

[http://dba.openoffice.org/ OOo Database Development] 
[http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA] 
[http://wiki.services.openoffice.org/wiki/Category:Database OOo General Database Info] 
 
 
: ''Initial author : [mailto:mechtilde@mechtilde@openoffice.org?subject:OOoWiki Mechtilde Stehmann] 24 September 2007''
: This page is under [http://creativecommons.org/licenses/by-sa/3.0/legalcode CC by-sa] since 2009-02-02
:''Please do not change the logical content of this site without acknowledge of the author or the [http://wiki.services.openoffice.org/wiki/Project_Lead OOo QA Project Lead/Co-Leads]. This side is linked by the online help.''

<div id="Template_CC-BY-SA">
{|align="left" width="100%" border="0" cellspacing="4" cellpadding="0" style="border-top: 1px solid #666; font-size: xx-small; margin-top: 20px; text-align: right;"
| Content on this page is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/legalcode Creative Common Attribution 3.0 license (CC BY-SA)].
|}
</div>

[[Category:Quality Assurance]]
[[Category:Database]]

Database

2009-02-25T09:16:08Z

Oj: /* English */

{{Database/Lang|Database}}
This page is hosted by the [http://wiki.services.openoffice.org/wiki/Database_Docu_Coordinator OOo Database Docu Coordinator], who are members of the [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team].
You can find here links to Base documentation ordered by languages and topics. Feel free to add documents, you are missing, to this list.

Resources related to OpenOffice.org Base:

= English =
The following links are in English.
== Manuals ==
=== General ===
* Base
: [[Documentation/Database | Database]]
: Description of the features of OpenOffice.org Base (short overview), Documentation resources and official sites

* OpenOffice.org User Guides (Getting started with Base) - ''PDF''
: [http://documentation.openoffice.org/manuals/oooauthors2/0110GS-GettingStartedWithBase.pdf Getting started with Base]
: Learn how to create a database, queries, forms and reports and connect to and use other data sources within OOo-Base.

* OpenOffice.org Base Manual
: [http://nothickmanuals.info/doku.php/articles:ooobaseprimer OpenOffice.org Base Primer]
: Initial Authors: Andrew 'Drew' Jensen, Frank Schoenheit, et al.
: A short screenshot-guided overview on how to use Base.

* Mid Level Base Tutorial
: [http://documentation.openoffice.org/servlets/ProjectDocumentList?folderID=778&expandFolder=778&folderID=597 Mid Level Base Tutorial]
: Innitial Authors: Mariano Casanova, Andrew 'Drew' Jensen

* Beginners - Example Database - Base Tutorial
: [http://www.oooforum.org/forum/viewtopic.phtml?t=25060 Example]
: Initial author: Andrew 'Drew' Jensen
: This tutorial covers creating a first database using OOoBase. It is intended for those that have not used Base before or those that have never used any database manager.

* Base and Macros
: [http://www.pitonyak.org/database/ Pitonyak's document]
: Initial author: Andrew Pitonyak
: This documentation focuses on operating a database with the help of OpenOffice.org Macros.

* Database: "ooBase", aka "Base"
: [http://sheepdogguides.com/fdb/fdb1main.htm Base Tutorial by Sheepdogguides.com]
: Initial author: TK Boyd
: After a short introduction some every day tasks like importing data from other tables are explained.

* Bringing data into OpenOffice 2.0's database
: [http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1222186,00.html Database]
: Initial author: Solveig Haugland
: Screenshot guided tutorial on how to import data into Openoffice.org Base.

* New Features in 3.1
: [[Base/New_features_in_3_1|New Features]]
: Initial author: Reizinger Zoltan
: Compiled from mailing list

=== Tables ===

* [[Standard Distributed Schema]]

=== Queries ===
* [[Built-in functions and Stored Procedures]]

=== Reports ===
* [[SUN Report Builder]]
: ''description followed''

* Sun Report Builder (Reference)
: [http://wiki.pentaho.com/display/Reporting/Pentaho+Reporting+Community+Documentation Reference]
: ''description follow ''

* Sun Report Builder Documentation
: [[SUN_Report_Builder/Documentation|Documentation]]
: Basic Features

* Functions in Reports
: [http://wiki.pentaho.com/display/Reporting/08.+Functions+and+Expressions Functions and Expressions]
: ''description follow - Not available now''

* Functions in Reports
: [[SUN Report Builder/Functions]]
: ''description followed''

=== Performance ===
: [http://wiki.services.openoffice.org/wiki/Base/Performance General Performance]

=== Developer ===
* Working basis to make the user guide better
: [[Documentation/OOoAuthors_User_Manual/Getting_Started/Getting_Started_with_Base | Getting_Started/Getting_Started_with_Base]]
: ''description followed''

* Using Macros in Database Files
: [[Macros_in_Database_Documents | Macros_in_Database_Documents]]
: 'Specification to develope this functionality

=== FAQ ===
* Common tasks
: [[Common_tasks | Common_tasks]]
: Initial author: Andrew 'Drew' Jensen
: Many good questions, no answers.

=== Misc ===
* HSQLDB Tips and Tricks
: [[HSQLDB:Tips_and_Tricks | Tips_and_Tricks]]
: ''description followed''

* [http://nothickmanuals.info/doku.php/articles:ooobaseprimer http://nothickmanuals.info/doku.php/articles:ooobaseprimer]

* [http://www.baseusers.com/index.html http://www.baseusers.com/index.html]

== Connecting ==
* Base New Driver Tutorial
: [[Base_New_Driver_Tutorial]]
: Initial author: Robert Vojta
: This small How-To contains a simple step-by-step introduction on how to put your driver inside the connectivity module. The second part of this document covers differences between a driver in connectivity module and a driver in an UNO package.

* Better Database Drivers
: [[BetterDatabaseDrivers]]
: Initial author:Eric Bischoff
:Some ideas for a better and simpler infrastructure for database drivers

* Connecting to Microsoft Access
: [[Connecting_to_Microsoft_Access]]
: Initial author: Regina Henschel
: These article describes how to connect to a Microsoft Access database file, if you use a MS Windows operating system.

* OpenOffice.org Base - Database Drivers
: [http://dba.openoffice.org/drivers/ http://dba.openoffice.org/drivers/]

* Connecting with MySQL
: [[Connect_MySQLandBase]]

* An overview page
: Native PostgreSQL Driver
: [http://dba.openoffice.org/drivers/postgresql/index.html http://dba.openoffice.org/drivers/postgresql/index.html]

* SQL-lite Driver
: http://dba.openoffice.org/drivers/sqlite/index.html

* mdb-sdbc-driver-0.1.0
: [http://dba.openoffice.org/drivers/mdb/index.html http://dba.openoffice.org/drivers/mdb/index.html]
: Initial author: Wind Li (yl146652 [at] openoffice [dot] org)
: It is a try to connect a Linux system to MS Access. There is no further development.

* A working page
: [[MDB_Driver_Integration]]

* MSA-Base Faq
: [[MSA-Base_Faq]]

* Firebird driver update for OO.org
: [http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=config:oobase Jaybird OpenOffice.org Base support]

== Examples ==
=== General ===
* Base Example (Overview)
: [[Category:Base_Example]]
: Initial author: Frank Schönheit

* Standard Distributed Schema
: [[Standard_Distributed_Schema]]

=== Concrete Examples ===
* A club membership database
: [[A_club_membership_database]]
: Initial author: Andrew 'Drew' Jensen
: Description of creating an example database

* OpenOffice.org API - Code snippets
: [http://codesnippets.services.openoffice.org/Database/index.xml http://codesnippets.services.openoffice.org/Database/index.xml]
: Useful code snippets solving frequently asked questions.

* Base Example
: [[Help_Files]]

== Misc ==

* [http://user.services.openoffice.org/en/forum/viewforum.php?f=13 OOo Community Forum]
: Initial author: Andrew 'Drew' Jensen
: Starting Point for all kind of OOo Database Questions

== Testing ==

* Main Point of OOo Database Testing
: [http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA Team Site]
: Initial Author: [[User:Clu Christoph Lukasiak]]

* Main Starter Document for QA Newbies
: [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html OOo QA How to Start Document]
: Initial Author: [[User:Wg Wolfram Garten]]

* [[Database_Automatic_Testing]]
* [[Documentation/OOoAuthors_User_Manual/Base_Guide/Planning |Base_Guide-Planning]]
* [[FAQ_%28Base%29 |FAQ Base]]
* [[OOoHelpOutline#Base_and_Database Base_and_Database]]

* [http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm http://ericzander.com/Publications/OO_MySQL_Tutorial/index.htm]
: Connecting OpenOffice.org To A Remote MySQL Database] (event. 1.x)

= French =

The following Links are showing French documents. If someone translate them we can show here the correponding links.

= German =

The following Links are showing German documents. If someone translate them we can show here the correponding links.

* [[DE/Beispielsdatenbank_mit_Base]]

* http://dannenhoefer.de/faqstarbasic/Datenbanken.html

* http://de.openoffice.org/doc/howto_2_0/index.html#datenquellen_2_0

* [[DE/FAQ/Base]]

* End user documentation
: http://www.ooowiki.de/KategorieBase

= Portugese =

The following Links are showing Portugese documents. If someone translate them we can show here the correponding links.

http://broffice.org/files/Introdu%C3%A7%C3%A3o_ao%20BrOffice.org_Base_2.0.x.odt

=Copyright=

[http://dba.openoffice.org/ OOo Database Development] 
[http://qa.openoffice.org/ooQAReloaded/DatabaseTeamsite/ooQA-TeamDatabase.html OOo Database QA] 
[http://wiki.services.openoffice.org/wiki/Category:Database OOo General Database Info] 
 
 
: ''Initial author : [mailto:mechtilde@mechtilde@openoffice.org?subject:OOoWiki Mechtilde Stehmann] 24 September 2007''
: This page is under [http://creativecommons.org/licenses/by-sa/3.0/legalcode CC by-sa] since 2009-02-02
:''Please do not change the logical content of this site without acknowledge of the author or the [http://wiki.services.openoffice.org/wiki/Project_Lead OOo QA Project Lead/Co-Leads]. This side is linked by the online help.''

<div id="Template_CC-BY-SA">
{|align="left" width="100%" border="0" cellspacing="4" cellpadding="0" style="border-top: 1px solid #666; font-size: xx-small; margin-top: 20px; text-align: right;"
| Content on this page is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/legalcode Creative Common Attribution 3.0 license (CC BY-SA)].
|}
</div>

[[Category:Quality Assurance]]
[[Category:Database]]

Base/Performance

2009-02-25T09:11:32Z

Oj:

== General ==
At the moment, this is just a basket to hold items I needed to remove from other pages. On the medium term, this is to be the central entry point for performance considerations in Base.

* opening forms
* starting the Java-based wizards
* creating a new HSQLDB (which implies starting the JVM)
* saving a form
* flickering when starting the New Database wizard from within the start center
* More speed for record operations / navigation

= Row Fetching =
We currently evaluate how row fetching can be accelerated. Fetching thousands of rows isn't as fast as it could be.

[[Category:Performance]]

Performance

2009-02-25T09:05:18Z

Oj: /* Work in progress */

== The performance project ==

This wiki page is the collaboration entry point for the [http://performance.openoffice.org/ OOo Performance project].

For questions and discussions, please use the new mailing list from the performance project: [mailto:dev@performance.openoffice.org dev@performance.openoffice.org]

When you plan to file an issue with regard to performance, please make sure to add the keyword <tt>performance</tt>

The official (incubator) project was started February 2009, but there have already been a lot of activities in this area in the past, so some of the information here (especially on the linked wiki pages) might be outdated.

This page will be cleaned up soon.

== To-Dos ==

Probably a lot - please [[Performance/To-Dos| continue here]].

== Work in progress ==

=== Startup ===
* [[Performance/Startup#Issues]]
* [http://wiki.services.openoffice.org/wiki/Performance/OOo31_LibrariesOnStartup Performance - Analysis (Windows)]
** [http://wiki.services.openoffice.org/wiki/Performance/OOo31_LibrariesOnStartup#File_I.2FO_during_OpenOffice.org_startup File I/O done by OpenOffice.org during startup]
** Measure cold startup time for OpenOffice.org 3.1 and svdem.exe (minimal VCL application)

=== Writer ===
* What's going on in Writer load/save performance [http://wiki.services.openoffice.org/wiki/Performance/WriterInProgress see here ]

=== Calc ===
{{:Calc/InProgress/Performance}}

=== Impress ===
* Impress OpenDocument load/save performance [[Impress/Performance#OpenDocument]]
* Impress slideshow performance [[Impress/Performance#Slideshow]]

=== Base ===
* [http://wiki.services.openoffice.org/wiki/Base/Performance General performance planning]
* [http://wiki.services.openoffice.org/wiki/Base/Performance#Row_Fetching Row fetching performance]

=== Load/Save General (Non Application Specific Tasks) ===

* [[RTLLogFileAnalysis|RTL_LOGFILE Analysis]]

== User Experience Index (UEI) ==
[http://wiki.services.openoffice.org/wiki/UEI UEI and Case Documents]

== Helpful Tooling and Resources ==

=== Test Environment ===
Popular reference configuration(use similar env on Hamburg and Beijing)
CPU: Core2 Duo 1.5~2G
Memory: 512M
OS: WindowsXP HOME

=== Test & Tuning Tools ===

* [[cold-start-simulator|Linux/cold-start]] simulator
* [[relocstat]] - dump relocation data
* [http://tools.openoffice.org/profiling/profiling-howto.html RTL_LOGFILE] - export RTL_LOGFILE=/tmp/foo
* [[valgrind]] - debug / trace memory usage
* [[callgrind]] - call graph profiler
* [[speedprof]] - a quick / hackish sampling full-stack-trace profiler & visualisation tool
* [[APPR]] - a performance regression tool suite
* [[Performance Related Test Documents]]
* [[Profiling_with_VTune|VTune]] - profiler for Windows and Linux, commercial product
* [[Performance/Tools/TrueTime|TrueTime]] - profiler for Windows, commercial product
* [http://developer.amd.com/cpu/CodeAnalyst/codeanalystwindows/Pages/default.aspx AMD CodeAnalyst] - profiler for windows, optimized for AMD, VisualStudio integration
* [[Performance/Tools/VerySleepy (HowTo)]] Very Sleepy 0.4 - open source profiler for windows, works on any cpu, very easy to use

=== Benchmarks & Description ===
If you have some benchmarks, share them here!

* [http://www.oooninja.com/2008/09/fastest-openofficeorg-edition-benchmark.html The Fastest OpenOffice.org Edition] comparison of four 2.4.1 editions on Fedora 9
* [http://www.oooninja.com/2008/05/openofficeorg-getting-faster-benchmark.html Is OpenOffice.org Getting Faster?] Comparison of 11 versions from 1.1.5 to 3.0.0 alpha

== Performance Test Results Distribution ==

=== Test results for different versions ===
* [http://wiki.services.openoffice.org/wiki/Performance/Performance_Work_2005 Performance 2005]
* [http://www.oooninja.com/2008/05/openofficeorg-getting-faster-benchmark.html Is OpenOffice.org Getting Faster?] benchmarks 5 common operations for OpenOffice.org versions 1.1.5 through 2.4.0 and DEV300_m3
* [[Performance/Startup/Linux| Startup of DEV300 builds on linux]]

== Integrated improvements ==
* [[Integrated_Performance_Improvements]]

== Other Pages ==
This Wiki page should become the ultimate authority on performance issues. Meanwhile, here are links to performance informationat other places
* [http://tools.openoffice.org/performance/ OpenOffice.org Performance Tuning page]
* [http://sw.openoffice.org/drafts/optimization.html Writer (SW, XML, Math, Linguistic) specific Optimizations]
* [http://tools.openoffice.org/performance/performance-activities-overview.html Current & Planned Performance Activities]

[[Category:Development]]
[[Category:Performance]]
[[Category:Database]]
[[Category:Effort]]
[[Category:Build_System]]

Database/Drivers/MySQL Native/Known Problems

2009-01-23T11:54:31Z

Oj: /* Wrong column width reported for text/binary columns */

{{DISPLAYTITLE:MySQL Native Driver: Known Problems}}

This page lists the currently known problems with the MySQL Native Driver, aka MySQL Connector/OOo.

== End User Observations ==

This section collects issues as observed by end users

=== Template for new entries ===

reported by NAME on 2009-mm-dd - needs review

Description goes here.

Severity: undecided

Reason: unknown

=== Binary columns are reported as text ===

Columns of type "LONG (VAR)BINARY" are reported as "LONG (VAR)CHAR" in the table designer

Severity: required

Reason: MySQL-internally, binary columns re-use existing types, e.g. MYSQL_TYPE_VAR_STRING for a VARBINARY column. The fact that the column is not text, but binary, is recorded in an additional per-column flag, where the BINARY_FLAG bit is set.
Unfortunately, this information is not transported via C/Cpp. Instead, the DATA_TYPE column of DatabaseMetaData.getColumns returns the untouched MYSQL_TYPE_, which alone is not sufficient to determine the proper column type.

Suggested solution: Either, DatabaseMetaData.getColumns must return additional information, e.g. an additional result set column, taking the column flags. Alternatively, the content of the DATA_TYPE column returned in getColumns must be "normalized", so that VARBINARY and VARCHAR in fact have different data types.

I'd somehow prefer the latter, as this is more future-proof. Also, since C/Cpp claims to have a JDBC-compliant API, it would be the better solution: In JDBC, [http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String) DATA_TYPE is defined] to contain a value from the java.sql.Types class, which already is a normalization we need ...

=== Copying tables may not work properly ===

reported by NAME on xx/01/2009 - needs review

'''Needs further and systematic testing!'''

Original table:

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
`col2` char(1) default NULL,
`col3` varchar(50) default NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`),
KEY `idx_col2` (`col2`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Copy:

CREATE TABLE `source2` (
`id` int(10) NOT NULL,
`col1` int(10) default NULL,
`col2` char(3) default NULL,
`col3` varchar(150) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

* Wrong column definitions (known issue)
* NOT NULL not properly handled
* Index information not copyied (same with JDBC, might be a Base issue)

Severity: undecided

Reason: unknown

=== Wrong column width reported for text/binary columns ===

reported by Ulf on 09/01/2009 - needs review

We discussed this before and it might be fixed in the current source, but I work on an older snapshot. We return number of bytes, OO.org wants number of characters. A typical follow-up error is that copying tables may fail and/or give wrong results.

From an earlier mail exchange:

Hintergrund: für eine VARBINARY(10)-Spalte in MySQL liefern wir aktuell
40, für eine INTEGER-Spalte in MySQL liefern wir aktuell 11. Wir liefern
momentan 40 für VARBINARY(10), weil das Feld maximal 10 Zeichen aufnehmen kann, die maximal 4 Bytes für das Encoding benötigen. Für ein VARCHAR(255) wird sogar VARCHAR(255) der Wert von 3060 geliefert, weil hier der MySQL Server nochmal in einem seiner Datenfelder einen Mul tiplikator von 3 einbaut (255 * 3 * 4 = 3060).

And:

Später am Abend fiel es mir wieder ein... wir ziehen getColumnDisplaySize() intern im Connector/C++ ran für ConnectionMetaData::getColumns() -> COLUMN_SIZE.
rs_data.push_back(my_i_to_a(buf, sizeof(buf)-1, (long) rs3_meta->getColumnDisplaySize(i))); // Column size

Pointer: MySQL ODBC file utitlity.c get_column_size

Severity: required

Reason: unknown

=== Renaming a view not possible ===

reported by Ulf on 09/01/2009 - needs review

Tested with the native driver: Its not possible to rename a view, the UI does not offer the context menu item when selecting the view in the table list.

Severity: desired

Reason: missing SDBCX support of the driver. In general, tables can only be renamed when there is a css.sdbcx.Table object representing a single table, which supports the XRename interface.

=== (JDBC) Renaming a view "makes" it a table ===

reported by Ulf on 09/01/2009 - needs review

Tested with the JDBC driver. Create a view and rename it in Base. Base changes the icon in the table list and shows the renamed object as a table :-)

Severity: low

Reason: unknown

=== Removing records from views fails ===

reported by Ulf on 08/01/2009

Removing records from SQL views neither works with the JDBC driver nor with the native driver. Base sends a misformed query like: "DELETE FROM `test`.`v` W"

Severity: low

Reason: Removing records from views is in general not possible in Base. The fact that "Edit/Delete record" is enabled for a view (as in any table which the user does not have the DELETE privilege for) is a bug, which I fixed in the CWS.

=== Empty schemata not shown ===

Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown.

Severity: desired

Reason: OOo calls getTables() - no tables - schema not displayed. Setting might even be cached - verify that database becomes visible after creating table (from mysql prompt) in schema.

=== OOo shows unrelated databases/schemata ===

Create a new Base database that connects to a MySQL schemata "test". Have "test" in the connection settings! OOo will ignore it and query MySQL for all tables in all schematas, and also display all those tables.

As a consequence the user will see all schemata he has access to not only the schemata/database "test" as requested in the connection settings

Severity: desired

=== No default schema on table creation ===

Base does not preselect a default schema in the table editor dialog. Its does not even if you connect to a certain schema by specifying it in the connection settings.

Severity: desired

=== No way to set MySQL specific table attributes ===

The Base table editor does not give access to table attributes. Not even basic ones such as the Engine (MyISAM: non-transactional, InnoDB: transactional).

Severity: 1.1

=== Base does not recognize schema changes ===

After connecting to a database and opening a table once, Base will not recognize changes applied to the DB schema meanwhile when opening the table in the table editor again.

Severity: low

that's not nice, but consistent with other DB/Drivers. For this purpose, there's View/Refresh Tables ...

=== Table column comments not synced between MySQL and Base ===

Base table column comments are not synchronized with the MySQL DB and its schema. Existing comments are not displayed in Base, and entering comments in the table editor is not propagated to MySQL.

Severity: later

That's a known issue with all database types. The column description as displayed in Base is purely client-side, and stored within the .odb file only. There's also an issue for this, but I'm too lazy too search for it right now ...

=== Violation of FK constraint gives two errors instead of one ===

Create two tables. Have one table "derived" reference entries in the other table "source". Try to remove a referenced record from the table "source". MySQL will report an error stating that you are violating a FK constrain. When using the MySQL JDBC driver the Base shows one requester with stating something like "Error - (error message from MySQL)". When using the native driver you get an requester stating "error" and you can proceed to an error details dialog. In the details dialog you will find two errors. The first has no message, the second shows the error message provided by MySQL.

This is a common pattern. Cause any SQL error and you can see up to three errors when you quit the initial requester using the button "more". Quite annoying, for example, when writing SQL statements for a Base "Query" object.

Severity: undecided

The empty error message is ugly, but not the only one within Base, so that's nothing which will block an 1.0 release ... (Ulf) But why does it work fine with the JDBC driver?

=== Default values not properly processed ===

The Base table editor neither properly sets default values nor does it re-engineer default values properly.

Severity: 1.1

Again, this is a known issue. The default value displayed in the UI is a so-called "control default", which is applied to ''controls'' used to enter data into the given field. The DB-side default for a column is a different property, API-wise, and currently not evaluated at all. Probably not even properly fetched by most existing drivers.

Changing this is possible, but probably requires UI changes. First, we would need to define how the control default and the DB default should interact in the UI. A possible scenario would be to drop the UI support for the control default, and always use the DB default (even in controls), as long as the driver supports providing/accepting DB defaults.

=== BIGINT values crippled ===

Large BIGINT values are displayed in Base using scientific notation: 1e+15. If one changes the display format to number #.### the first 14 values of a large number (9223372036854775807) are displayed properly but then some rounding takes place, for example: 9223372036854800000. Connector/C++ can handle long long (L64) values properly and Base does use getLong() nevertheless the displayed value seems wrong.

Severity: undecided

I bet that's because of the number formatter ... processing numbers for display is done using a office-wide number formatter component. Unfortunately, it works with double-precision values only, which imposes a precision loss for certain values. This applies to "too-large" values, as well as fractional values with "too many" digits. This is a general problem in Base, and not limited to the MySQL Native Driver.

A possible solution would be to '''not'' employ the number formatter for certain column types. (Effectively, this means ''not'' using a <code>FormattedField</code> for the respective table column in the data view, but a NumericField, which internally works with long integer values of arbitrary (?) length.) This would solve the BIGINT issue, though not the too-many-digits issue for fractional values.

=== Tools -> User Administration does not work ===

When you choose <code>Tools/User administration...</code>, you're presented with an error.

Severity: required (remove the menu item)

Severity: required (implement proper user administration)

=== create table with wizard fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

run table wizard: take default & all field & push finish → java assertion list appears

Severity: required

Reason: unknown

=== change pk fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

open table with pk and change pk to any other field -> error: duplicate entry for key

Severity: required

Reason: pk not detected?

=== change table fieldtype in edit view not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

open table in edit mode -> fieldtypes greyed out (not possible to change)

Severity: required

Reason: The driver does not support <code>XAlterTable</code> (and more SDBCX-level interfaces)

=== fieldtype is changed after saving ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

in table edit view: create a field from f.e. type bool & save → tinyint

Severity: required

Reason: maybe the same problem like 1.10 & 1.11

(Ulf) Duplicate and not an error in C/C++. There is no boolean type in MySQL. However, its handled in the JDBC driver case, the best we can do is emulate it in the same way.

=== copy table & paste special fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

copy table & paste special (change tablename) with pk → invalid error message without text appears

Severity: required

Reason: unknown

=== query wizard shows 'query' as 'table' ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

create any query, open query wizard → tables listbox propose query (also with the other wizards)

Severity: required

Reason: unknown

== Developer Observations ==

This section collects observations interesting for developers only. It's likely the describe the root cause for another problem listed in the ''End User Observations'' section. In this sense, they might be duplicates, but we currently just use this as reminder list whenever we notice a problem ...

=== Do we need any of those? ===

ERROR: SQL Exception ODatabaseMetaData::getCrossReference: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getProcedures: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getUDTs: feature not implemented.
ERROR: SQL exception ODatabaseMetaData::supportsIntegrityEnhancementFacility: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::supportsResultSetConcurrency: feature not implemented.

=== INSERT does not work ===

Inserting data into a simple table does not work. Works fine when using the JDBC driver.

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Severity: required

=== information_schema (I_S) not shown in schema list ===

SHOW DATABASES shows the I_S. When quering the I_S for schema, the I_S will not expose itself. Different versions of Connector/C++ use different ways to fetch schema lists. Until and including Alpha SHOW DATABSES is used.

When using the JDBC driver and specifying no database in the connection URL no schemata are shown at all.

Severity: undecided

=== DatabseMetaData::getColumns() COLUMN_SIZE ===

DatabseMetaData::getColumns() takes COLUMN_SIZE from getDisplaySize().

Affected: DECIMAL/FLOAT/VARCHAR.

Severity: required

Note: DisplaySize is not the same as ColumnSize. The former is a hint for UI processors which are to display the data in a tabular way. Currently, Base does not make use of this attribute.
The ColumnSize's semantics is described in the [http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String) Java API], and Base uses it in the very same semantics.
As a consequence, COLUMN_SIZE is what needs to be tweaked.

=== DatabseMetaData::getColumns() DECIMAL_DIGITS ===

DatabseMetaData::getColumns() does not set DECIMAL_DIGITS. Therefore, Base does not show it properly.

=== Perfoemance problem when accessing big tables ===

Open a table with more then 1000 rows. Jump to last one. => 2 min.

Severity: required

== Potential Issues ==

This section serves as collection of issues which might become a problem to end users, though we did not yet (bother to) create scenarios where users are hit by those (potential) problems.

=== TIME value range ===

[http://dev.mysql.com/doc/refman/5.1/en/time.html|MySQL's TIME] data type may have a significantly larger value range than the Base counterpart.

Severity: undecided

=== TINYINT / BOOLEAN ===

Educate Base users on [http://dev.mysql.com/doc/refman/5.1/en/other-vendor-data-types.html MySQL Server type mappings], for example BOOL[EAN] -> TINYINT.

== fixed ==

=== Tools -> Relations... not working ===

FIXED: Error message: Database not support relations.
ERROR: Still not possible to create new relations.

We should hint MySQL users in the driver documentation that Base takes no(?) measures to clean up no longer needed indexes. MySQL's InnoDB needs some special treatment.

Severity: required

With 3.x, Base is able to administrate MySQL's relationships (via the ODBC/JDBC bridge), so the native driver should be able to do this, too. At least with approximately the same set of bugs as the "old" driver :)

=== insert data in table not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

create any table with pk → not possible to insert data into table

Severity: required

Investigation: The driver currently returns an empty result set when being asked for the table privileges: <code>getTablePrivileges( null, "schema", "table" )</code>. Debugging deeper seems to indicate that parsing the result of a "SHOW GRANTS" query is flawed.

=== Tools->SQL does not show error message ===

reported by Ulf on 08/01/2009

Open the SQL execution wizard by invoking Tools->SQL. Run an invalid SQL query, for example, "create table foo". Base prints a new line "n:" in the status part of the window but it shows no error message.

Severity: required

=== New tables shown after "refresh tables" but (delete) rights/grants wrong? ===

reported by Ulf on 08/01/2009

Create some tables in MySQL. Start Base and browse the table list. Create a new table in MySQL (not in Base!), make sure it has a PK, add some records. Select View->Refresh tables. Base will show the new table. Try to remove a row from the newly created table. Base rejects the delete operation stating that the user as insufficient rights.

Investigation: This is a general problem currently, <code>DatabaseMetaData::getTablePrivileges</code> returns wrong data (all the time? sometimes? andrey claimed to have fixed this, but the fix does not work for me). If I fake the getTablePrivileges implementation to return the full set of privileges regardless the table being asked for, then the problem does not happen.

=== DECIMAL shown as TEXT ===

Base shows numerical DECIMAL columns as TEXT (in the table editor?).

Severity: required

Investigation: column is reported as <code>MYSQL_TYPE_NEWDECIMAL</code>, which wasn't covered in C/OOo (which only had a case for <code>MYSQL_TYPE_DECIMAL</code>)
=== Subforms do not work ===

Well, some of them do ... more precisely, SQL statements with named parameters (":param_name") do not work in general. The ODBC/JDBC driver wrapper used to replace them with unnamed parameters ("?"), 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.

Severity: required

Fixing this should be easy, at least so it is as usable as with other DBs/drivers, in particular with the existing MySQL-(O/J)DBC bridge. Before sending statements to the server, the driver must replace (unless the statement's <code>EscapeProcessing</code> is <code>FALSE</code>, of course) named parameters with anonymous ones. The disadvantage is that this only works when Base itself can parse the statement, and that it potentially changes the statement. However, both statements are true for all other DBs which do not support named parameters, too.

=== SMALLINT shown as REAL ===

When loading a table with a SMALLINT column it is shown as a FLOAT/REAL column in Base (in the table editor?)

Severity: required

Database/Drivers/MySQL Native/Known Problems

2009-01-23T10:56:12Z

Oj: /* Tools -> Relations... not working */

{{DISPLAYTITLE:MySQL Native Driver: Known Problems}}

This page lists the currently known problems with the MySQL Native Driver, aka MySQL Connector/OOo.

== End User Observations ==

This section collects issues as observed by end users

=== Template for new entries ===

reported by NAME on xx/01/2009 - needs review

Description goes here.

Severity: undecided

Reason: unknown

=== Copying tables may not work properly ===

reported by NAME on xx/01/2009 - needs review

'''Needs further and systematic testing!'''

Original table:

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
`col2` char(1) default NULL,
`col3` varchar(50) default NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`),
KEY `idx_col2` (`col2`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Copy:

CREATE TABLE `source2` (
`id` int(10) NOT NULL,
`col1` int(10) default NULL,
`col2` char(3) default NULL,
`col3` varchar(150) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

* Wrong column definitions (known issue)
* NOT NULL not properly handled
* Index information not copyied (same with JDBC, might be a Base issue)

Severity: undecided

Reason: unknown

=== Wrong column width reported for text/binary columns ===

reported by Ulf on 09/01/2009 - needs review

We discussed this before and it might be fixed in the current source, but I work on an older snapshot. We return number of bytes, OO.org wants number of characters. A typical follow-up error is that copying tables may fail and/or give wrong results.

From an earlier mail exchange:

Hintergrund: für eine VARBINARY(10)-Spalte in MySQL liefern wir aktuell
40, für eine INTEGER-Spalte in MySQL liefern wir aktuell 11. Wir liefern
momentan 40 für VARBINARY(10), weil das Feld maximal 10 Zeichen aufnehmen kann, die maximal 4 Bytes für das Encoding benötigen. Für ein VARCHAR(255) wird sogar VARCHAR(255) der Wert von 3060 geliefert, weil hier der MySQL Server nochmal in einem seiner Datenfelder einen Mul tiplikator von 3 einbaut (255 * 3 * 4 = 3060).

And:

Später am Abend fiel es mir wieder ein... wir ziehen getColumnDisplaySize() intern im Connector/C++ ran für ConnectionMetaData::getColumns() -> COLUMN_SIZE.
rs_data.push_back(my_i_to_a(buf, sizeof(buf)-1, (long) rs3_meta->getColumnDisplaySize(i))); // Column size

Severity: required

Reason: unknown

=== Renaming a view not possible ===

reported by Ulf on 09/01/2009 - needs review

Tested with the native driver: Its not possible to rename a view, the UI does not offer the context menu item when selecting the view in the table list.

Severity: desired

Reason: missing SDBCX support of the driver. In general, tables can only be renamed when there is a css.sdbcx.Table object representing a single table, which supports the XRename interface.

=== (JDBC) Renaming a view "makes" it a table ===

reported by Ulf on 09/01/2009 - needs review

Tested with the JDBC driver. Create a view and rename it in Base. Base changes the icon in the table list and shows the renamed object as a table :-)

Severity: low

Reason: unknown

=== Removing records from views fails ===

reported by Ulf on 08/01/2009

Removing records from SQL views neither works with the JDBC driver nor with the native driver. Base sends a misformed query like: "DELETE FROM `test`.`v` W"

Severity: low

Reason: Removing records from views is in general not possible in Base. The fact that "Edit/Delete record" is enabled for a view (as in any table which the user does not have the DELETE privilege for) is a bug, which I fixed in the CWS.

=== Empty schemata not shown ===

Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown.

Severity: desired

Reason: OOo calls getTables() - no tables - schema not displayed. Setting might even be cached - verify that database becomes visible after creating table (from mysql prompt) in schema.

=== OOo shows unrelated databases/schemata ===

Create a new Base database that connects to a MySQL schemata "test". Have "test" in the connection settings! OOo will ignore it and query MySQL for all tables in all schematas, and also display all those tables.

As a consequence the user will see all schemata he has access to not only the schemata/database "test" as requested in the connection settings

Severity: desired

=== No default schema on table creation ===

Base does not preselect a default schema in the table editor dialog. Its does not even if you connect to a certain schema by specifying it in the connection settings.

Severity: desired

=== No way to set MySQL specific table attributes ===

The Base table editor does not give access to table attributes. Not even basic ones such as the Engine (MyISAM: non-transactional, InnoDB: transactional).

Severity: 1.1

=== Base does not recognize schema changes ===

After connecting to a database and opening a table once, Base will not recognize changes applied to the DB schema meanwhile when opening the table in the table editor again.

Severity: low

that's not nice, but consistent with other DB/Drivers. For this purpose, there's View/Refresh Tables ...

=== Table column comments not synced between MySQL and Base ===

Base table column comments are not synchronized with the MySQL DB and its schema. Existing comments are not displayed in Base, and entering comments in the table editor is not propagated to MySQL.

Severity: later

That's a known issue with all database types. The column description as displayed in Base is purely client-side, and stored within the .odb file only. There's also an issue for this, but I'm too lazy too search for it right now ...

=== Violation of FK constraint gives two errors instead of one ===

Create two tables. Have one table "derived" reference entries in the other table "source". Try to remove a referenced record from the table "source". MySQL will report an error stating that you are violating a FK constrain. When using the MySQL JDBC driver the Base shows one requester with stating something like "Error - (error message from MySQL)". When using the native driver you get an requester stating "error" and you can proceed to an error details dialog. In the details dialog you will find two errors. The first has no message, the second shows the error message provided by MySQL.

This is a common pattern. Cause any SQL error and you can see up to three errors when you quit the initial requester using the button "more". Quite annoying, for example, when writing SQL statements for a Base "Query" object.

Severity: undecided

The empty error message is ugly, but not the only one within Base, so that's nothing which will block an 1.0 release ... (Ulf) But why does it work fine with the JDBC driver?

=== Default values not properly processed ===

The Base table editor neither properly sets default values nor does it re-engineer default values properly.

Severity: 1.1

Again, this is a known issue. The default value displayed in the UI is a so-called "control default", which is applied to ''controls'' used to enter data into the given field. The DB-side default for a column is a different property, API-wise, and currently not evaluated at all. Probably not even properly fetched by most existing drivers.

Changing this is possible, but probably requires UI changes. First, we would need to define how the control default and the DB default should interact in the UI. A possible scenario would be to drop the UI support for the control default, and always use the DB default (even in controls), as long as the driver supports providing/accepting DB defaults.

=== BIGINT values crippled ===

Large BIGINT values are displayed in Base using scientific notation: 1e+15. If one changes the display format to number #.### the first 14 values of a large number (9223372036854775807) are displayed properly but then some rounding takes place, for example: 9223372036854800000. Connector/C++ can handle long long (L64) values properly and Base does use getLong() nevertheless the displayed value seems wrong.

Severity: undecided

I bet that's because of the number formatter ... processing numbers for display is done using a office-wide number formatter component. Unfortunately, it works with double-precision values only, which imposes a precision loss for certain values. This applies to "too-large" values, as well as fractional values with "too many" digits. This is a general problem in Base, and not limited to the MySQL Native Driver.

A possible solution would be to '''not'' employ the number formatter for certain column types. (Effectively, this means ''not'' using a <code>FormattedField</code> for the respective table column in the data view, but a NumericField, which internally works with long integer values of arbitrary (?) length.) This would solve the BIGINT issue, though not the too-many-digits issue for fractional values.

=== Tools -> User Administration does not work ===

When you choose <code>Tools/User administration...</code>, you're presented with an error.

Severity: required (remove the menu item)

Severity: required (implement proper user administration)

=== create table with wizard fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

run table wizard: take default & all field & push finish → java assertion list appears

Severity: required

Reason: unknown

=== change pk fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

open table with pk and change pk to any other field -> error: duplicate entry for key

Severity: required

Reason: pk not detected?

=== change table fieldtype in edit view not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

open table in edit mode -> fieldtypes greyed out (not possible to change)

Severity: required

Reason: The driver does not support <code>XAlterTable</code> (and more SDBCX-level interfaces)

=== fieldtype is changed after saving ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

in table edit view: create a field from f.e. type bool & save → tinyint

Severity: required

Reason: maybe the same problem like 1.10 & 1.11

(Ulf) Duplicate and not an error in C/C++. There is no boolean type in MySQL. However, its handled in the JDBC driver case, the best we can do is emulate it in the same way.

=== copy table & paste special fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

copy table & paste special (change tablename) with pk → invalid error message without text appears

Severity: required

Reason: unknown

=== query wizard shows 'query' as 'table' ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

create any query, open query wizard → tables listbox propose query (also with the other wizards)

Severity: required

Reason: unknown

== Developer Observations ==

This section collects observations interesting for developers only. It's likely the describe the root cause for another problem listed in the ''End User Observations'' section. In this sense, they might be duplicates, but we currently just use this as reminder list whenever we notice a problem ...

=== Do we need any of those? ===

ERROR: SQL Exception ODatabaseMetaData::getCrossReference: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getProcedures: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getUDTs: feature not implemented.
ERROR: SQL exception ODatabaseMetaData::supportsIntegrityEnhancementFacility: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::supportsResultSetConcurrency: feature not implemented.

=== INSERT does not work ===

Inserting data into a simple table does not work. Works fine when using the JDBC driver.

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Severity: required

=== information_schema (I_S) not shown in schema list ===

SHOW DATABASES shows the I_S. When quering the I_S for schema, the I_S will not expose itself. Different versions of Connector/C++ use different ways to fetch schema lists. Until and including Alpha SHOW DATABSES is used.

When using the JDBC driver and specifying no database in the connection URL no schemata are shown at all.

Severity: undecided

=== DatabseMetaData::getColumns() COLUMN_SIZE ===

DatabseMetaData::getColumns() takes COLUMN_SIZE from getDisplaySize().

Affected: DECIMAL/FLOAT/VARCHAR.

Severity: required

Note: DisplaySize is not the same as ColumnSize. The former is a hint for UI processors which are to display the data in a tabular way. Currently, Base does not make use of this attribute.
The ColumnSize's semantics is described in the [http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String) Java API], and Base uses it in the very same semantics.
As a consequence, COLUMN_SIZE is what needs to be tweaked.

=== DatabseMetaData::getColumns() DECIMAL_DIGITS ===

DatabseMetaData::getColumns() does not set DECIMAL_DIGITS. Therefore, Base does not show it properly.

=== Perfoemance problem when accessing big tables ===

Open a table with more then 1000 rows. Jump to last one. => 2 min.

Severity: required

== Potential Issues ==

This section serves as collection of issues which might become a problem to end users, though we did not yet (bother to) create scenarios where users are hit by those (potential) problems.

=== TIME value range ===

[http://dev.mysql.com/doc/refman/5.1/en/time.html|MySQL's TIME] data type may have a significantly larger value range than the Base counterpart.

Severity: undecided

=== TINYINT / BOOLEAN ===

Educate Base users on [http://dev.mysql.com/doc/refman/5.1/en/other-vendor-data-types.html MySQL Server type mappings], for example BOOL[EAN] -> TINYINT.

== fixed ==

=== Tools -> Relations... not working ===

FIXED: Error message: Database not support relations.
ERROR: Still not possible to create new relations.

We should hint MySQL users in the driver documentation that Base takes no(?) measures to clean up no longer needed indexes. MySQL's InnoDB needs some special treatment.

Severity: required

With 3.x, Base is able to administrate MySQL's relationships (via the ODBC/JDBC bridge), so the native driver should be able to do this, too. At least with approximately the same set of bugs as the "old" driver :)

=== insert data in table not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

create any table with pk → not possible to insert data into table

Severity: required

Investigation: The driver currently returns an empty result set when being asked for the table privileges: <code>getTablePrivileges( null, "schema", "table" )</code>. Debugging deeper seems to indicate that parsing the result of a "SHOW GRANTS" query is flawed.

=== Tools->SQL does not show error message ===

reported by Ulf on 08/01/2009

Open the SQL execution wizard by invoking Tools->SQL. Run an invalid SQL query, for example, "create table foo". Base prints a new line "n:" in the status part of the window but it shows no error message.

Severity: required

=== New tables shown after "refresh tables" but (delete) rights/grants wrong? ===

reported by Ulf on 08/01/2009

Create some tables in MySQL. Start Base and browse the table list. Create a new table in MySQL (not in Base!), make sure it has a PK, add some records. Select View->Refresh tables. Base will show the new table. Try to remove a row from the newly created table. Base rejects the delete operation stating that the user as insufficient rights.

Investigation: This is a general problem currently, <code>DatabaseMetaData::getTablePrivileges</code> returns wrong data (all the time? sometimes? andrey claimed to have fixed this, but the fix does not work for me). If I fake the getTablePrivileges implementation to return the full set of privileges regardless the table being asked for, then the problem does not happen.

=== DECIMAL shown as TEXT ===

Base shows numerical DECIMAL columns as TEXT (in the table editor?).

Severity: required

Investigation: column is reported as <code>MYSQL_TYPE_NEWDECIMAL</code>, which wasn't covered in C/OOo (which only had a case for <code>MYSQL_TYPE_DECIMAL</code>)
=== Subforms do not work ===

Well, some of them do ... more precisely, SQL statements with named parameters (":param_name") do not work in general. The ODBC/JDBC driver wrapper used to replace them with unnamed parameters ("?"), 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.

Severity: required

Fixing this should be easy, at least so it is as usable as with other DBs/drivers, in particular with the existing MySQL-(O/J)DBC bridge. Before sending statements to the server, the driver must replace (unless the statement's <code>EscapeProcessing</code> is <code>FALSE</code>, of course) named parameters with anonymous ones. The disadvantage is that this only works when Base itself can parse the statement, and that it potentially changes the statement. However, both statements are true for all other DBs which do not support named parameters, too.

=== SMALLINT shown as REAL ===

When loading a table with a SMALLINT column it is shown as a FLOAT/REAL column in Base (in the table editor?)

Severity: required

Database/Drivers/MySQL Native/Known Problems

2009-01-23T10:49:21Z

Oj: /* DatabseMetaData::getColumns() COLUMN_SIZE */

{{DISPLAYTITLE:MySQL Native Driver: Known Problems}}

This page lists the currently known problems with the MySQL Native Driver, aka MySQL Connector/OOo.

== End User Observations ==

This section collects issues as observed by end users

=== Template for new entries ===

reported by NAME on xx/01/2009 - needs review

Description goes here.

Severity: undecided

Reason: unknown

=== Copying tables may not work properly ===

reported by NAME on xx/01/2009 - needs review

'''Needs further and systematic testing!'''

Original table:

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
`col2` char(1) default NULL,
`col3` varchar(50) default NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`),
KEY `idx_col2` (`col2`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Copy:

CREATE TABLE `source2` (
`id` int(10) NOT NULL,
`col1` int(10) default NULL,
`col2` char(3) default NULL,
`col3` varchar(150) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

* Wrong column definitions (known issue)
* NOT NULL not properly handled
* Index information not copyied (same with JDBC, might be a Base issue)

Severity: undecided

Reason: unknown

=== Wrong column width reported for text/binary columns ===

reported by Ulf on 09/01/2009 - needs review

We discussed this before and it might be fixed in the current source, but I work on an older snapshot. We return number of bytes, OO.org wants number of characters. A typical follow-up error is that copying tables may fail and/or give wrong results.

From an earlier mail exchange:

Hintergrund: für eine VARBINARY(10)-Spalte in MySQL liefern wir aktuell
40, für eine INTEGER-Spalte in MySQL liefern wir aktuell 11. Wir liefern
momentan 40 für VARBINARY(10), weil das Feld maximal 10 Zeichen aufnehmen kann, die maximal 4 Bytes für das Encoding benötigen. Für ein VARCHAR(255) wird sogar VARCHAR(255) der Wert von 3060 geliefert, weil hier der MySQL Server nochmal in einem seiner Datenfelder einen Mul tiplikator von 3 einbaut (255 * 3 * 4 = 3060).

And:

Später am Abend fiel es mir wieder ein... wir ziehen getColumnDisplaySize() intern im Connector/C++ ran für ConnectionMetaData::getColumns() -> COLUMN_SIZE.
rs_data.push_back(my_i_to_a(buf, sizeof(buf)-1, (long) rs3_meta->getColumnDisplaySize(i))); // Column size

Severity: required

Reason: unknown

=== Renaming a view not possible ===

reported by Ulf on 09/01/2009 - needs review

Tested with the native driver: Its not possible to rename a view, the UI does not offer the context menu item when selecting the view in the table list.

Severity: desired

Reason: missing SDBCX support of the driver. In general, tables can only be renamed when there is a css.sdbcx.Table object representing a single table, which supports the XRename interface.

=== (JDBC) Renaming a view "makes" it a table ===

reported by Ulf on 09/01/2009 - needs review

Tested with the JDBC driver. Create a view and rename it in Base. Base changes the icon in the table list and shows the renamed object as a table :-)

Severity: low

Reason: unknown

=== Removing records from views fails ===

reported by Ulf on 08/01/2009

Removing records from SQL views neither works with the JDBC driver nor with the native driver. Base sends a misformed query like: "DELETE FROM `test`.`v` W"

Severity: low

Reason: Removing records from views is in general not possible in Base. The fact that "Edit/Delete record" is enabled for a view (as in any table which the user does not have the DELETE privilege for) is a bug, which I fixed in the CWS.

=== Empty schemata not shown ===

Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown.

Severity: desired

Reason: OOo calls getTables() - no tables - schema not displayed. Setting might even be cached - verify that database becomes visible after creating table (from mysql prompt) in schema.

=== OOo shows unrelated databases/schemata ===

Create a new Base database that connects to a MySQL schemata "test". Have "test" in the connection settings! OOo will ignore it and query MySQL for all tables in all schematas, and also display all those tables.

As a consequence the user will see all schemata he has access to not only the schemata/database "test" as requested in the connection settings

Severity: desired

=== No default schema on table creation ===

Base does not preselect a default schema in the table editor dialog. Its does not even if you connect to a certain schema by specifying it in the connection settings.

Severity: desired

=== No way to set MySQL specific table attributes ===

The Base table editor does not give access to table attributes. Not even basic ones such as the Engine (MyISAM: non-transactional, InnoDB: transactional).

Severity: 1.1

=== Base does not recognize schema changes ===

After connecting to a database and opening a table once, Base will not recognize changes applied to the DB schema meanwhile when opening the table in the table editor again.

Severity: low

that's not nice, but consistent with other DB/Drivers. For this purpose, there's View/Refresh Tables ...

=== Table column comments not synced between MySQL and Base ===

Base table column comments are not synchronized with the MySQL DB and its schema. Existing comments are not displayed in Base, and entering comments in the table editor is not propagated to MySQL.

Severity: later

That's a known issue with all database types. The column description as displayed in Base is purely client-side, and stored within the .odb file only. There's also an issue for this, but I'm too lazy too search for it right now ...

=== Violation of FK constraint gives two errors instead of one ===

Create two tables. Have one table "derived" reference entries in the other table "source". Try to remove a referenced record from the table "source". MySQL will report an error stating that you are violating a FK constrain. When using the MySQL JDBC driver the Base shows one requester with stating something like "Error - (error message from MySQL)". When using the native driver you get an requester stating "error" and you can proceed to an error details dialog. In the details dialog you will find two errors. The first has no message, the second shows the error message provided by MySQL.

This is a common pattern. Cause any SQL error and you can see up to three errors when you quit the initial requester using the button "more". Quite annoying, for example, when writing SQL statements for a Base "Query" object.

Severity: undecided

The empty error message is ugly, but not the only one within Base, so that's nothing which will block an 1.0 release ... (Ulf) But why does it work fine with the JDBC driver?

=== Default values not properly processed ===

The Base table editor neither properly sets default values nor does it re-engineer default values properly.

Severity: 1.1

Again, this is a known issue. The default value displayed in the UI is a so-called "control default", which is applied to ''controls'' used to enter data into the given field. The DB-side default for a column is a different property, API-wise, and currently not evaluated at all. Probably not even properly fetched by most existing drivers.

Changing this is possible, but probably requires UI changes. First, we would need to define how the control default and the DB default should interact in the UI. A possible scenario would be to drop the UI support for the control default, and always use the DB default (even in controls), as long as the driver supports providing/accepting DB defaults.

=== BIGINT values crippled ===

Large BIGINT values are displayed in Base using scientific notation: 1e+15. If one changes the display format to number #.### the first 14 values of a large number (9223372036854775807) are displayed properly but then some rounding takes place, for example: 9223372036854800000. Connector/C++ can handle long long (L64) values properly and Base does use getLong() nevertheless the displayed value seems wrong.

Severity: undecided

I bet that's because of the number formatter ... processing numbers for display is done using a office-wide number formatter component. Unfortunately, it works with double-precision values only, which imposes a precision loss for certain values. This applies to "too-large" values, as well as fractional values with "too many" digits. This is a general problem in Base, and not limited to the MySQL Native Driver.

A possible solution would be to '''not'' employ the number formatter for certain column types. (Effectively, this means ''not'' using a <code>FormattedField</code> for the respective table column in the data view, but a NumericField, which internally works with long integer values of arbitrary (?) length.) This would solve the BIGINT issue, though not the too-many-digits issue for fractional values.

=== Tools -> User Administration does not work ===

When you choose <code>Tools/User administration...</code>, you're presented with an error.

Severity: required (remove the menu item)

Severity: required (implement proper user administration)

=== create table with wizard fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

run table wizard: take default & all field & push finish → java assertion list appears

Severity: required

Reason: unknown

=== change pk fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

open table with pk and change pk to any other field -> error: duplicate entry for key

Severity: required

Reason: pk not detected?

=== change table fieldtype in edit view not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

open table in edit mode -> fieldtypes greyed out (not possible to change)

Severity: required

Reason: The driver does not support <code>XAlterTable</code> (and more SDBCX-level interfaces)

=== fieldtype is changed after saving ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

in table edit view: create a field from f.e. type bool & save → tinyint

Severity: required

Reason: maybe the same problem like 1.10 & 1.11

(Ulf) Duplicate and not an error in C/C++. There is no boolean type in MySQL. However, its handled in the JDBC driver case, the best we can do is emulate it in the same way.

=== copy table & paste special fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

copy table & paste special (change tablename) with pk → invalid error message without text appears

Severity: required

Reason: unknown

=== query wizard shows 'query' as 'table' ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

create any query, open query wizard → tables listbox propose query (also with the other wizards)

Severity: required

Reason: unknown

== Developer Observations ==

This section collects observations interesting for developers only. It's likely the describe the root cause for another problem listed in the ''End User Observations'' section. In this sense, they might be duplicates, but we currently just use this as reminder list whenever we notice a problem ...

=== Do we need any of those? ===

ERROR: SQL Exception ODatabaseMetaData::getCrossReference: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getProcedures: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getUDTs: feature not implemented.
ERROR: SQL exception ODatabaseMetaData::supportsIntegrityEnhancementFacility: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::supportsResultSetConcurrency: feature not implemented.

=== INSERT does not work ===

Inserting data into a simple table does not work. Works fine when using the JDBC driver.

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Severity: required

=== information_schema (I_S) not shown in schema list ===

SHOW DATABASES shows the I_S. When quering the I_S for schema, the I_S will not expose itself. Different versions of Connector/C++ use different ways to fetch schema lists. Until and including Alpha SHOW DATABSES is used.

When using the JDBC driver and specifying no database in the connection URL no schemata are shown at all.

Severity: undecided

=== DatabseMetaData::getColumns() COLUMN_SIZE ===

DatabseMetaData::getColumns() takes COLUMN_SIZE from getDisplaySize().

Affected: DECIMAL/FLOAT/VARCHAR.

Severity: required

Note: DisplaySize is not the same as ColumnSize. The former is a hint for UI processors which are to display the data in a tabular way. Currently, Base does not make use of this attribute.
The ColumnSize's semantics is described in the [http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String) Java API], and Base uses it in the very same semantics.
As a consequence, COLUMN_SIZE is what needs to be tweaked.

=== DatabseMetaData::getColumns() DECIMAL_DIGITS ===

DatabseMetaData::getColumns() does not set DECIMAL_DIGITS. Therefore, Base does not show it properly.

=== Perfoemance problem when accessing big tables ===

Open a table with more then 1000 rows. Jump to last one. => 2 min.

Severity: required

== Potential Issues ==

This section serves as collection of issues which might become a problem to end users, though we did not yet (bother to) create scenarios where users are hit by those (potential) problems.

=== TIME value range ===

[http://dev.mysql.com/doc/refman/5.1/en/time.html|MySQL's TIME] data type may have a significantly larger value range than the Base counterpart.

Severity: undecided

=== TINYINT / BOOLEAN ===

Educate Base users on [http://dev.mysql.com/doc/refman/5.1/en/other-vendor-data-types.html MySQL Server type mappings], for example BOOL[EAN] -> TINYINT.

== fixed ==

=== Tools -> Relations... not working ===

Error message: Database not support relations.

We should hint MySQL users in the driver documentation that Base takes no(?) measures to clean up no longer needed indexes. MySQL's InnoDB needs some special treatment.

Severity: required

With 3.x, Base is able to administrate MySQL's relationships (via the ODBC/JDBC bridge), so the native driver should be able to do this, too. At least with approximately the same set of bugs as the "old" driver :)

=== insert data in table not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

create any table with pk → not possible to insert data into table

Severity: required

Investigation: The driver currently returns an empty result set when being asked for the table privileges: <code>getTablePrivileges( null, "schema", "table" )</code>. Debugging deeper seems to indicate that parsing the result of a "SHOW GRANTS" query is flawed.

=== Tools->SQL does not show error message ===

reported by Ulf on 08/01/2009

Open the SQL execution wizard by invoking Tools->SQL. Run an invalid SQL query, for example, "create table foo". Base prints a new line "n:" in the status part of the window but it shows no error message.

Severity: required

=== New tables shown after "refresh tables" but (delete) rights/grants wrong? ===

reported by Ulf on 08/01/2009

Create some tables in MySQL. Start Base and browse the table list. Create a new table in MySQL (not in Base!), make sure it has a PK, add some records. Select View->Refresh tables. Base will show the new table. Try to remove a row from the newly created table. Base rejects the delete operation stating that the user as insufficient rights.

Investigation: This is a general problem currently, <code>DatabaseMetaData::getTablePrivileges</code> returns wrong data (all the time? sometimes? andrey claimed to have fixed this, but the fix does not work for me). If I fake the getTablePrivileges implementation to return the full set of privileges regardless the table being asked for, then the problem does not happen.

=== DECIMAL shown as TEXT ===

Base shows numerical DECIMAL columns as TEXT (in the table editor?).

Severity: required

Investigation: column is reported as <code>MYSQL_TYPE_NEWDECIMAL</code>, which wasn't covered in C/OOo (which only had a case for <code>MYSQL_TYPE_DECIMAL</code>)
=== Subforms do not work ===

Well, some of them do ... more precisely, SQL statements with named parameters (":param_name") do not work in general. The ODBC/JDBC driver wrapper used to replace them with unnamed parameters ("?"), 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.

Severity: required

Fixing this should be easy, at least so it is as usable as with other DBs/drivers, in particular with the existing MySQL-(O/J)DBC bridge. Before sending statements to the server, the driver must replace (unless the statement's <code>EscapeProcessing</code> is <code>FALSE</code>, of course) named parameters with anonymous ones. The disadvantage is that this only works when Base itself can parse the statement, and that it potentially changes the statement. However, both statements are true for all other DBs which do not support named parameters, too.

=== SMALLINT shown as REAL ===

When loading a table with a SMALLINT column it is shown as a FLOAT/REAL column in Base (in the table editor?)

Severity: required

Database/Drivers/MySQL Native/Known Problems

2009-01-23T10:41:48Z

Oj: /* fixed */

{{DISPLAYTITLE:MySQL Native Driver: Known Problems}}

This page lists the currently known problems with the MySQL Native Driver, aka MySQL Connector/OOo.

== End User Observations ==

This section collects issues as observed by end users

=== Template for new entries ===

reported by NAME on xx/01/2009 - needs review

Description goes here.

Severity: undecided

Reason: unknown

=== Copying tables may not work properly ===

reported by NAME on xx/01/2009 - needs review

'''Needs further and systematic testing!'''

Original table:

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
`col2` char(1) default NULL,
`col3` varchar(50) default NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`),
KEY `idx_col2` (`col2`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Copy:

CREATE TABLE `source2` (
`id` int(10) NOT NULL,
`col1` int(10) default NULL,
`col2` char(3) default NULL,
`col3` varchar(150) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

* Wrong column definitions (known issue)
* NOT NULL not properly handled
* Index information not copyied (same with JDBC, might be a Base issue)

Severity: undecided

Reason: unknown

=== Wrong column width reported for text/binary columns ===

reported by Ulf on 09/01/2009 - needs review

We discussed this before and it might be fixed in the current source, but I work on an older snapshot. We return number of bytes, OO.org wants number of characters. A typical follow-up error is that copying tables may fail and/or give wrong results.

From an earlier mail exchange:

Hintergrund: für eine VARBINARY(10)-Spalte in MySQL liefern wir aktuell
40, für eine INTEGER-Spalte in MySQL liefern wir aktuell 11. Wir liefern
momentan 40 für VARBINARY(10), weil das Feld maximal 10 Zeichen aufnehmen kann, die maximal 4 Bytes für das Encoding benötigen. Für ein VARCHAR(255) wird sogar VARCHAR(255) der Wert von 3060 geliefert, weil hier der MySQL Server nochmal in einem seiner Datenfelder einen Mul tiplikator von 3 einbaut (255 * 3 * 4 = 3060).

And:

Später am Abend fiel es mir wieder ein... wir ziehen getColumnDisplaySize() intern im Connector/C++ ran für ConnectionMetaData::getColumns() -> COLUMN_SIZE.
rs_data.push_back(my_i_to_a(buf, sizeof(buf)-1, (long) rs3_meta->getColumnDisplaySize(i))); // Column size

Severity: required

Reason: unknown

=== Renaming a view not possible ===

reported by Ulf on 09/01/2009 - needs review

Tested with the native driver: Its not possible to rename a view, the UI does not offer the context menu item when selecting the view in the table list.

Severity: desired

Reason: missing SDBCX support of the driver. In general, tables can only be renamed when there is a css.sdbcx.Table object representing a single table, which supports the XRename interface.

=== (JDBC) Renaming a view "makes" it a table ===

reported by Ulf on 09/01/2009 - needs review

Tested with the JDBC driver. Create a view and rename it in Base. Base changes the icon in the table list and shows the renamed object as a table :-)

Severity: low

Reason: unknown

=== Removing records from views fails ===

reported by Ulf on 08/01/2009

Removing records from SQL views neither works with the JDBC driver nor with the native driver. Base sends a misformed query like: "DELETE FROM `test`.`v` W"

Severity: low

Reason: Removing records from views is in general not possible in Base. The fact that "Edit/Delete record" is enabled for a view (as in any table which the user does not have the DELETE privilege for) is a bug, which I fixed in the CWS.

=== Empty schemata not shown ===

Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown.

Severity: desired

Reason: OOo calls getTables() - no tables - schema not displayed. Setting might even be cached - verify that database becomes visible after creating table (from mysql prompt) in schema.

=== OOo shows unrelated databases/schemata ===

Create a new Base database that connects to a MySQL schemata "test". Have "test" in the connection settings! OOo will ignore it and query MySQL for all tables in all schematas, and also display all those tables.

As a consequence the user will see all schemata he has access to not only the schemata/database "test" as requested in the connection settings

Severity: desired

=== No default schema on table creation ===

Base does not preselect a default schema in the table editor dialog. Its does not even if you connect to a certain schema by specifying it in the connection settings.

Severity: desired

=== No way to set MySQL specific table attributes ===

The Base table editor does not give access to table attributes. Not even basic ones such as the Engine (MyISAM: non-transactional, InnoDB: transactional).

Severity: 1.1

=== Base does not recognize schema changes ===

After connecting to a database and opening a table once, Base will not recognize changes applied to the DB schema meanwhile when opening the table in the table editor again.

Severity: low

that's not nice, but consistent with other DB/Drivers. For this purpose, there's View/Refresh Tables ...

=== Table column comments not synced between MySQL and Base ===

Base table column comments are not synchronized with the MySQL DB and its schema. Existing comments are not displayed in Base, and entering comments in the table editor is not propagated to MySQL.

Severity: later

That's a known issue with all database types. The column description as displayed in Base is purely client-side, and stored within the .odb file only. There's also an issue for this, but I'm too lazy too search for it right now ...

=== Violation of FK constraint gives two errors instead of one ===

Create two tables. Have one table "derived" reference entries in the other table "source". Try to remove a referenced record from the table "source". MySQL will report an error stating that you are violating a FK constrain. When using the MySQL JDBC driver the Base shows one requester with stating something like "Error - (error message from MySQL)". When using the native driver you get an requester stating "error" and you can proceed to an error details dialog. In the details dialog you will find two errors. The first has no message, the second shows the error message provided by MySQL.

This is a common pattern. Cause any SQL error and you can see up to three errors when you quit the initial requester using the button "more". Quite annoying, for example, when writing SQL statements for a Base "Query" object.

Severity: undecided

The empty error message is ugly, but not the only one within Base, so that's nothing which will block an 1.0 release ... (Ulf) But why does it work fine with the JDBC driver?

=== Default values not properly processed ===

The Base table editor neither properly sets default values nor does it re-engineer default values properly.

Severity: 1.1

Again, this is a known issue. The default value displayed in the UI is a so-called "control default", which is applied to ''controls'' used to enter data into the given field. The DB-side default for a column is a different property, API-wise, and currently not evaluated at all. Probably not even properly fetched by most existing drivers.

Changing this is possible, but probably requires UI changes. First, we would need to define how the control default and the DB default should interact in the UI. A possible scenario would be to drop the UI support for the control default, and always use the DB default (even in controls), as long as the driver supports providing/accepting DB defaults.

=== BIGINT values crippled ===

Large BIGINT values are displayed in Base using scientific notation: 1e+15. If one changes the display format to number #.### the first 14 values of a large number (9223372036854775807) are displayed properly but then some rounding takes place, for example: 9223372036854800000. Connector/C++ can handle long long (L64) values properly and Base does use getLong() nevertheless the displayed value seems wrong.

Severity: undecided

I bet that's because of the number formatter ... processing numbers for display is done using a office-wide number formatter component. Unfortunately, it works with double-precision values only, which imposes a precision loss for certain values. This applies to "too-large" values, as well as fractional values with "too many" digits. This is a general problem in Base, and not limited to the MySQL Native Driver.

A possible solution would be to '''not'' employ the number formatter for certain column types. (Effectively, this means ''not'' using a <code>FormattedField</code> for the respective table column in the data view, but a NumericField, which internally works with long integer values of arbitrary (?) length.) This would solve the BIGINT issue, though not the too-many-digits issue for fractional values.

=== Tools -> User Administration does not work ===

When you choose <code>Tools/User administration...</code>, you're presented with an error.

Severity: required (remove the menu item)

Severity: required (implement proper user administration)

=== create table with wizard fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

run table wizard: take default & all field & push finish → java assertion list appears

Severity: required

Reason: unknown

=== change pk fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

open table with pk and change pk to any other field -> error: duplicate entry for key

Severity: required

Reason: pk not detected?

=== change table fieldtype in edit view not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

open table in edit mode -> fieldtypes greyed out (not possible to change)

Severity: required

Reason: The driver does not support <code>XAlterTable</code> (and more SDBCX-level interfaces)

=== fieldtype is changed after saving ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

in table edit view: create a field from f.e. type bool & save → tinyint

Severity: required

Reason: maybe the same problem like 1.10 & 1.11

(Ulf) Duplicate and not an error in C/C++. There is no boolean type in MySQL. However, its handled in the JDBC driver case, the best we can do is emulate it in the same way.

=== copy table & paste special fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

copy table & paste special (change tablename) with pk → invalid error message without text appears

Severity: required

Reason: unknown

=== query wizard shows 'query' as 'table' ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

create any query, open query wizard → tables listbox propose query (also with the other wizards)

Severity: required

Reason: unknown

== Developer Observations ==

This section collects observations interesting for developers only. It's likely the describe the root cause for another problem listed in the ''End User Observations'' section. In this sense, they might be duplicates, but we currently just use this as reminder list whenever we notice a problem ...

=== Do we need any of those? ===

ERROR: SQL Exception ODatabaseMetaData::getCrossReference: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getProcedures: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getUDTs: feature not implemented.
ERROR: SQL exception ODatabaseMetaData::supportsIntegrityEnhancementFacility: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::supportsResultSetConcurrency: feature not implemented.

=== INSERT does not work ===

Inserting data into a simple table does not work. Works fine when using the JDBC driver.

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Severity: required

=== information_schema (I_S) not shown in schema list ===

SHOW DATABASES shows the I_S. When quering the I_S for schema, the I_S will not expose itself. Different versions of Connector/C++ use different ways to fetch schema lists. Until and including Alpha SHOW DATABSES is used.

When using the JDBC driver and specifying no database in the connection URL no schemata are shown at all.

Severity: undecided

=== DatabseMetaData::getColumns() COLUMN_SIZE ===

DatabseMetaData::getColumns() takes COLUMN_SIZE from getDisplaySize().

Affected: DECIMAL/FLOAT.

Severity: required

Note: DisplaySize is not the same as ColumnSize. The former is a hint for UI processors which are to display the data in a tabular way. Currently, Base does not make use of this attribute.
The ColumnSize's semantics is described in the [http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String) Java API], and Base uses it in the very same semantics.
As a consequence, COLUMN_SIZE is what needs to be tweaked.

=== DatabseMetaData::getColumns() DECIMAL_DIGITS ===

DatabseMetaData::getColumns() does not set DECIMAL_DIGITS. Therefore, Base does not show it properly.

=== Perfoemance problem when accessing big tables ===

Open a table with more then 1000 rows. Jump to last one. => 2 min.

Severity: required

== Potential Issues ==

This section serves as collection of issues which might become a problem to end users, though we did not yet (bother to) create scenarios where users are hit by those (potential) problems.

=== TIME value range ===

[http://dev.mysql.com/doc/refman/5.1/en/time.html|MySQL's TIME] data type may have a significantly larger value range than the Base counterpart.

Severity: undecided

=== TINYINT / BOOLEAN ===

Educate Base users on [http://dev.mysql.com/doc/refman/5.1/en/other-vendor-data-types.html MySQL Server type mappings], for example BOOL[EAN] -> TINYINT.

== fixed ==

=== Tools -> Relations... not working ===

Error message: Database not support relations.

We should hint MySQL users in the driver documentation that Base takes no(?) measures to clean up no longer needed indexes. MySQL's InnoDB needs some special treatment.

Severity: required

With 3.x, Base is able to administrate MySQL's relationships (via the ODBC/JDBC bridge), so the native driver should be able to do this, too. At least with approximately the same set of bugs as the "old" driver :)

=== insert data in table not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

create any table with pk → not possible to insert data into table

Severity: required

Investigation: The driver currently returns an empty result set when being asked for the table privileges: <code>getTablePrivileges( null, "schema", "table" )</code>. Debugging deeper seems to indicate that parsing the result of a "SHOW GRANTS" query is flawed.

=== Tools->SQL does not show error message ===

reported by Ulf on 08/01/2009

Open the SQL execution wizard by invoking Tools->SQL. Run an invalid SQL query, for example, "create table foo". Base prints a new line "n:" in the status part of the window but it shows no error message.

Severity: required

=== New tables shown after "refresh tables" but (delete) rights/grants wrong? ===

reported by Ulf on 08/01/2009

Create some tables in MySQL. Start Base and browse the table list. Create a new table in MySQL (not in Base!), make sure it has a PK, add some records. Select View->Refresh tables. Base will show the new table. Try to remove a row from the newly created table. Base rejects the delete operation stating that the user as insufficient rights.

Investigation: This is a general problem currently, <code>DatabaseMetaData::getTablePrivileges</code> returns wrong data (all the time? sometimes? andrey claimed to have fixed this, but the fix does not work for me). If I fake the getTablePrivileges implementation to return the full set of privileges regardless the table being asked for, then the problem does not happen.

=== DECIMAL shown as TEXT ===

Base shows numerical DECIMAL columns as TEXT (in the table editor?).

Severity: required

Investigation: column is reported as <code>MYSQL_TYPE_NEWDECIMAL</code>, which wasn't covered in C/OOo (which only had a case for <code>MYSQL_TYPE_DECIMAL</code>)
=== Subforms do not work ===

Well, some of them do ... more precisely, SQL statements with named parameters (":param_name") do not work in general. The ODBC/JDBC driver wrapper used to replace them with unnamed parameters ("?"), 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.

Severity: required

Fixing this should be easy, at least so it is as usable as with other DBs/drivers, in particular with the existing MySQL-(O/J)DBC bridge. Before sending statements to the server, the driver must replace (unless the statement's <code>EscapeProcessing</code> is <code>FALSE</code>, of course) named parameters with anonymous ones. The disadvantage is that this only works when Base itself can parse the statement, and that it potentially changes the statement. However, both statements are true for all other DBs which do not support named parameters, too.

=== SMALLINT shown as REAL ===

When loading a table with a SMALLINT column it is shown as a FLOAT/REAL column in Base (in the table editor?)

Severity: required

Database/Drivers/MySQL Native/Known Problems

2009-01-23T10:41:32Z

Oj: /* End User Observations */

{{DISPLAYTITLE:MySQL Native Driver: Known Problems}}

This page lists the currently known problems with the MySQL Native Driver, aka MySQL Connector/OOo.

== End User Observations ==

This section collects issues as observed by end users

=== Template for new entries ===

reported by NAME on xx/01/2009 - needs review

Description goes here.

Severity: undecided

Reason: unknown

=== Copying tables may not work properly ===

reported by NAME on xx/01/2009 - needs review

'''Needs further and systematic testing!'''

Original table:

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
`col2` char(1) default NULL,
`col3` varchar(50) default NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`),
KEY `idx_col2` (`col2`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Copy:

CREATE TABLE `source2` (
`id` int(10) NOT NULL,
`col1` int(10) default NULL,
`col2` char(3) default NULL,
`col3` varchar(150) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

* Wrong column definitions (known issue)
* NOT NULL not properly handled
* Index information not copyied (same with JDBC, might be a Base issue)

Severity: undecided

Reason: unknown

=== Wrong column width reported for text/binary columns ===

reported by Ulf on 09/01/2009 - needs review

We discussed this before and it might be fixed in the current source, but I work on an older snapshot. We return number of bytes, OO.org wants number of characters. A typical follow-up error is that copying tables may fail and/or give wrong results.

From an earlier mail exchange:

Hintergrund: für eine VARBINARY(10)-Spalte in MySQL liefern wir aktuell
40, für eine INTEGER-Spalte in MySQL liefern wir aktuell 11. Wir liefern
momentan 40 für VARBINARY(10), weil das Feld maximal 10 Zeichen aufnehmen kann, die maximal 4 Bytes für das Encoding benötigen. Für ein VARCHAR(255) wird sogar VARCHAR(255) der Wert von 3060 geliefert, weil hier der MySQL Server nochmal in einem seiner Datenfelder einen Mul tiplikator von 3 einbaut (255 * 3 * 4 = 3060).

And:

Später am Abend fiel es mir wieder ein... wir ziehen getColumnDisplaySize() intern im Connector/C++ ran für ConnectionMetaData::getColumns() -> COLUMN_SIZE.
rs_data.push_back(my_i_to_a(buf, sizeof(buf)-1, (long) rs3_meta->getColumnDisplaySize(i))); // Column size

Severity: required

Reason: unknown

=== Renaming a view not possible ===

reported by Ulf on 09/01/2009 - needs review

Tested with the native driver: Its not possible to rename a view, the UI does not offer the context menu item when selecting the view in the table list.

Severity: desired

Reason: missing SDBCX support of the driver. In general, tables can only be renamed when there is a css.sdbcx.Table object representing a single table, which supports the XRename interface.

=== (JDBC) Renaming a view "makes" it a table ===

reported by Ulf on 09/01/2009 - needs review

Tested with the JDBC driver. Create a view and rename it in Base. Base changes the icon in the table list and shows the renamed object as a table :-)

Severity: low

Reason: unknown

=== Removing records from views fails ===

reported by Ulf on 08/01/2009

Removing records from SQL views neither works with the JDBC driver nor with the native driver. Base sends a misformed query like: "DELETE FROM `test`.`v` W"

Severity: low

Reason: Removing records from views is in general not possible in Base. The fact that "Edit/Delete record" is enabled for a view (as in any table which the user does not have the DELETE privilege for) is a bug, which I fixed in the CWS.

=== Empty schemata not shown ===

Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown.

Severity: desired

Reason: OOo calls getTables() - no tables - schema not displayed. Setting might even be cached - verify that database becomes visible after creating table (from mysql prompt) in schema.

=== OOo shows unrelated databases/schemata ===

Create a new Base database that connects to a MySQL schemata "test". Have "test" in the connection settings! OOo will ignore it and query MySQL for all tables in all schematas, and also display all those tables.

As a consequence the user will see all schemata he has access to not only the schemata/database "test" as requested in the connection settings

Severity: desired

=== No default schema on table creation ===

Base does not preselect a default schema in the table editor dialog. Its does not even if you connect to a certain schema by specifying it in the connection settings.

Severity: desired

=== No way to set MySQL specific table attributes ===

The Base table editor does not give access to table attributes. Not even basic ones such as the Engine (MyISAM: non-transactional, InnoDB: transactional).

Severity: 1.1

=== Base does not recognize schema changes ===

After connecting to a database and opening a table once, Base will not recognize changes applied to the DB schema meanwhile when opening the table in the table editor again.

Severity: low

that's not nice, but consistent with other DB/Drivers. For this purpose, there's View/Refresh Tables ...

=== Table column comments not synced between MySQL and Base ===

Base table column comments are not synchronized with the MySQL DB and its schema. Existing comments are not displayed in Base, and entering comments in the table editor is not propagated to MySQL.

Severity: later

That's a known issue with all database types. The column description as displayed in Base is purely client-side, and stored within the .odb file only. There's also an issue for this, but I'm too lazy too search for it right now ...

=== Violation of FK constraint gives two errors instead of one ===

Create two tables. Have one table "derived" reference entries in the other table "source". Try to remove a referenced record from the table "source". MySQL will report an error stating that you are violating a FK constrain. When using the MySQL JDBC driver the Base shows one requester with stating something like "Error - (error message from MySQL)". When using the native driver you get an requester stating "error" and you can proceed to an error details dialog. In the details dialog you will find two errors. The first has no message, the second shows the error message provided by MySQL.

This is a common pattern. Cause any SQL error and you can see up to three errors when you quit the initial requester using the button "more". Quite annoying, for example, when writing SQL statements for a Base "Query" object.

Severity: undecided

The empty error message is ugly, but not the only one within Base, so that's nothing which will block an 1.0 release ... (Ulf) But why does it work fine with the JDBC driver?

=== Default values not properly processed ===

The Base table editor neither properly sets default values nor does it re-engineer default values properly.

Severity: 1.1

Again, this is a known issue. The default value displayed in the UI is a so-called "control default", which is applied to ''controls'' used to enter data into the given field. The DB-side default for a column is a different property, API-wise, and currently not evaluated at all. Probably not even properly fetched by most existing drivers.

Changing this is possible, but probably requires UI changes. First, we would need to define how the control default and the DB default should interact in the UI. A possible scenario would be to drop the UI support for the control default, and always use the DB default (even in controls), as long as the driver supports providing/accepting DB defaults.

=== BIGINT values crippled ===

Large BIGINT values are displayed in Base using scientific notation: 1e+15. If one changes the display format to number #.### the first 14 values of a large number (9223372036854775807) are displayed properly but then some rounding takes place, for example: 9223372036854800000. Connector/C++ can handle long long (L64) values properly and Base does use getLong() nevertheless the displayed value seems wrong.

Severity: undecided

I bet that's because of the number formatter ... processing numbers for display is done using a office-wide number formatter component. Unfortunately, it works with double-precision values only, which imposes a precision loss for certain values. This applies to "too-large" values, as well as fractional values with "too many" digits. This is a general problem in Base, and not limited to the MySQL Native Driver.

A possible solution would be to '''not'' employ the number formatter for certain column types. (Effectively, this means ''not'' using a <code>FormattedField</code> for the respective table column in the data view, but a NumericField, which internally works with long integer values of arbitrary (?) length.) This would solve the BIGINT issue, though not the too-many-digits issue for fractional values.

=== Tools -> User Administration does not work ===

When you choose <code>Tools/User administration...</code>, you're presented with an error.

Severity: required (remove the menu item)

Severity: required (implement proper user administration)

=== create table with wizard fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

run table wizard: take default & all field & push finish → java assertion list appears

Severity: required

Reason: unknown

=== change pk fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

open table with pk and change pk to any other field -> error: duplicate entry for key

Severity: required

Reason: pk not detected?

=== change table fieldtype in edit view not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

open table in edit mode -> fieldtypes greyed out (not possible to change)

Severity: required

Reason: The driver does not support <code>XAlterTable</code> (and more SDBCX-level interfaces)

=== fieldtype is changed after saving ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

in table edit view: create a field from f.e. type bool & save → tinyint

Severity: required

Reason: maybe the same problem like 1.10 & 1.11

(Ulf) Duplicate and not an error in C/C++. There is no boolean type in MySQL. However, its handled in the JDBC driver case, the best we can do is emulate it in the same way.

=== copy table & paste special fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

copy table & paste special (change tablename) with pk → invalid error message without text appears

Severity: required

Reason: unknown

=== query wizard shows 'query' as 'table' ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

create any query, open query wizard → tables listbox propose query (also with the other wizards)

Severity: required

Reason: unknown

== Developer Observations ==

This section collects observations interesting for developers only. It's likely the describe the root cause for another problem listed in the ''End User Observations'' section. In this sense, they might be duplicates, but we currently just use this as reminder list whenever we notice a problem ...

=== Do we need any of those? ===

ERROR: SQL Exception ODatabaseMetaData::getCrossReference: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getProcedures: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getUDTs: feature not implemented.
ERROR: SQL exception ODatabaseMetaData::supportsIntegrityEnhancementFacility: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::supportsResultSetConcurrency: feature not implemented.

=== INSERT does not work ===

Inserting data into a simple table does not work. Works fine when using the JDBC driver.

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Severity: required

=== information_schema (I_S) not shown in schema list ===

SHOW DATABASES shows the I_S. When quering the I_S for schema, the I_S will not expose itself. Different versions of Connector/C++ use different ways to fetch schema lists. Until and including Alpha SHOW DATABSES is used.

When using the JDBC driver and specifying no database in the connection URL no schemata are shown at all.

Severity: undecided

=== DatabseMetaData::getColumns() COLUMN_SIZE ===

DatabseMetaData::getColumns() takes COLUMN_SIZE from getDisplaySize().

Affected: DECIMAL/FLOAT.

Severity: required

Note: DisplaySize is not the same as ColumnSize. The former is a hint for UI processors which are to display the data in a tabular way. Currently, Base does not make use of this attribute.
The ColumnSize's semantics is described in the [http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String) Java API], and Base uses it in the very same semantics.
As a consequence, COLUMN_SIZE is what needs to be tweaked.

=== DatabseMetaData::getColumns() DECIMAL_DIGITS ===

DatabseMetaData::getColumns() does not set DECIMAL_DIGITS. Therefore, Base does not show it properly.

=== Perfoemance problem when accessing big tables ===

Open a table with more then 1000 rows. Jump to last one. => 2 min.

Severity: required

== Potential Issues ==

This section serves as collection of issues which might become a problem to end users, though we did not yet (bother to) create scenarios where users are hit by those (potential) problems.

=== TIME value range ===

[http://dev.mysql.com/doc/refman/5.1/en/time.html|MySQL's TIME] data type may have a significantly larger value range than the Base counterpart.

Severity: undecided

=== TINYINT / BOOLEAN ===

Educate Base users on [http://dev.mysql.com/doc/refman/5.1/en/other-vendor-data-types.html MySQL Server type mappings], for example BOOL[EAN] -> TINYINT.

== fixed ==

=== Tools -> Relations... not working ===

Error message: Database not support relations.

We should hint MySQL users in the driver documentation that Base takes no(?) measures to clean up no longer needed indexes. MySQL's InnoDB needs some special treatment.

Severity: required

With 3.x, Base is able to administrate MySQL's relationships (via the ODBC/JDBC bridge), so the native driver should be able to do this, too. At least with approximately the same set of bugs as the "old" driver :)

=== insert data in table not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

create any table with pk → not possible to insert data into table

Severity: required

Investigation: The driver currently returns an empty result set when being asked for the table privileges: <code>getTablePrivileges( null, "schema", "table" )</code>. Debugging deeper seems to indicate that parsing the result of a "SHOW GRANTS" query is flawed.

=== Tools->SQL does not show error message ===

reported by Ulf on 08/01/2009

Open the SQL execution wizard by invoking Tools->SQL. Run an invalid SQL query, for example, "create table foo". Base prints a new line "n:" in the status part of the window but it shows no error message.

Severity: required

=== New tables shown after "refresh tables" but (delete) rights/grants wrong? ===

reported by Ulf on 08/01/2009

Create some tables in MySQL. Start Base and browse the table list. Create a new table in MySQL (not in Base!), make sure it has a PK, add some records. Select View->Refresh tables. Base will show the new table. Try to remove a row from the newly created table. Base rejects the delete operation stating that the user as insufficient rights.

Investigation: This is a general problem currently, <code>DatabaseMetaData::getTablePrivileges</code> returns wrong data (all the time? sometimes? andrey claimed to have fixed this, but the fix does not work for me). If I fake the getTablePrivileges implementation to return the full set of privileges regardless the table being asked for, then the problem does not happen.

=== DECIMAL shown as TEXT ===

Base shows numerical DECIMAL columns as TEXT (in the table editor?).

Severity: required

Investigation: column is reported as <code>MYSQL_TYPE_NEWDECIMAL</code>, which wasn't covered in C/OOo (which only had a case for <code>MYSQL_TYPE_DECIMAL</code>)
=== Subforms do not work ===

Well, some of them do ... more precisely, SQL statements with named parameters (":param_name") do not work in general. The ODBC/JDBC driver wrapper used to replace them with unnamed parameters ("?"), 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.

Severity: required

Fixing this should be easy, at least so it is as usable as with other DBs/drivers, in particular with the existing MySQL-(O/J)DBC bridge. Before sending statements to the server, the driver must replace (unless the statement's <code>EscapeProcessing</code> is <code>FALSE</code>, of course) named parameters with anonymous ones. The disadvantage is that this only works when Base itself can parse the statement, and that it potentially changes the statement. However, both statements are true for all other DBs which do not support named parameters, too.

Database/Drivers/MySQL Native/Known Problems

2009-01-23T10:38:01Z

Oj: /* fixed */

{{DISPLAYTITLE:MySQL Native Driver: Known Problems}}

This page lists the currently known problems with the MySQL Native Driver, aka MySQL Connector/OOo.

== End User Observations ==

This section collects issues as observed by end users

=== Template for new entries ===

reported by NAME on xx/01/2009 - needs review

Description goes here.

Severity: undecided

Reason: unknown

=== Copying tables may not work properly ===

reported by NAME on xx/01/2009 - needs review

'''Needs further and systematic testing!'''

Original table:

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
`col2` char(1) default NULL,
`col3` varchar(50) default NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`),
KEY `idx_col2` (`col2`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Copy:

CREATE TABLE `source2` (
`id` int(10) NOT NULL,
`col1` int(10) default NULL,
`col2` char(3) default NULL,
`col3` varchar(150) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

* Wrong column definitions (known issue)
* NOT NULL not properly handled
* Index information not copyied (same with JDBC, might be a Base issue)

Severity: undecided

Reason: unknown

=== Wrong column width reported for text/binary columns ===

reported by Ulf on 09/01/2009 - needs review

We discussed this before and it might be fixed in the current source, but I work on an older snapshot. We return number of bytes, OO.org wants number of characters. A typical follow-up error is that copying tables may fail and/or give wrong results.

From an earlier mail exchange:

Hintergrund: für eine VARBINARY(10)-Spalte in MySQL liefern wir aktuell
40, für eine INTEGER-Spalte in MySQL liefern wir aktuell 11. Wir liefern
momentan 40 für VARBINARY(10), weil das Feld maximal 10 Zeichen aufnehmen kann, die maximal 4 Bytes für das Encoding benötigen. Für ein VARCHAR(255) wird sogar VARCHAR(255) der Wert von 3060 geliefert, weil hier der MySQL Server nochmal in einem seiner Datenfelder einen Mul tiplikator von 3 einbaut (255 * 3 * 4 = 3060).

And:

Später am Abend fiel es mir wieder ein... wir ziehen getColumnDisplaySize() intern im Connector/C++ ran für ConnectionMetaData::getColumns() -> COLUMN_SIZE.
rs_data.push_back(my_i_to_a(buf, sizeof(buf)-1, (long) rs3_meta->getColumnDisplaySize(i))); // Column size

Severity: required

Reason: unknown

=== Renaming a view not possible ===

reported by Ulf on 09/01/2009 - needs review

Tested with the native driver: Its not possible to rename a view, the UI does not offer the context menu item when selecting the view in the table list.

Severity: desired

Reason: missing SDBCX support of the driver. In general, tables can only be renamed when there is a css.sdbcx.Table object representing a single table, which supports the XRename interface.

=== (JDBC) Renaming a view "makes" it a table ===

reported by Ulf on 09/01/2009 - needs review

Tested with the JDBC driver. Create a view and rename it in Base. Base changes the icon in the table list and shows the renamed object as a table :-)

Severity: low

Reason: unknown

=== Removing records from views fails ===

reported by Ulf on 08/01/2009

Removing records from SQL views neither works with the JDBC driver nor with the native driver. Base sends a misformed query like: "DELETE FROM `test`.`v` W"

Severity: low

Reason: Removing records from views is in general not possible in Base. The fact that "Edit/Delete record" is enabled for a view (as in any table which the user does not have the DELETE privilege for) is a bug, which I fixed in the CWS.

=== Empty schemata not shown ===

Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown.

Severity: desired

Reason: OOo calls getTables() - no tables - schema not displayed. Setting might even be cached - verify that database becomes visible after creating table (from mysql prompt) in schema.

=== SMALLINT shown as REAL ===

When loading a table with a SMALLINT column it is shown as a FLOAT/REAL column in Base (in the table editor?)

Severity: required

=== OOo shows unrelated databases/schemata ===

Create a new Base database that connects to a MySQL schemata "test". Have "test" in the connection settings! OOo will ignore it and query MySQL for all tables in all schematas, and also display all those tables.

As a consequence the user will see all schemata he has access to not only the schemata/database "test" as requested in the connection settings

Severity: desired

=== No default schema on table creation ===

Base does not preselect a default schema in the table editor dialog. Its does not even if you connect to a certain schema by specifying it in the connection settings.

Severity: desired

=== No way to set MySQL specific table attributes ===

The Base table editor does not give access to table attributes. Not even basic ones such as the Engine (MyISAM: non-transactional, InnoDB: transactional).

Severity: 1.1

=== Base does not recognize schema changes ===

After connecting to a database and opening a table once, Base will not recognize changes applied to the DB schema meanwhile when opening the table in the table editor again.

Severity: low

that's not nice, but consistent with other DB/Drivers. For this purpose, there's View/Refresh Tables ...

=== Table column comments not synced between MySQL and Base ===

Base table column comments are not synchronized with the MySQL DB and its schema. Existing comments are not displayed in Base, and entering comments in the table editor is not propagated to MySQL.

Severity: later

That's a known issue with all database types. The column description as displayed in Base is purely client-side, and stored within the .odb file only. There's also an issue for this, but I'm too lazy too search for it right now ...

=== Violation of FK constraint gives two errors instead of one ===

Create two tables. Have one table "derived" reference entries in the other table "source". Try to remove a referenced record from the table "source". MySQL will report an error stating that you are violating a FK constrain. When using the MySQL JDBC driver the Base shows one requester with stating something like "Error - (error message from MySQL)". When using the native driver you get an requester stating "error" and you can proceed to an error details dialog. In the details dialog you will find two errors. The first has no message, the second shows the error message provided by MySQL.

This is a common pattern. Cause any SQL error and you can see up to three errors when you quit the initial requester using the button "more". Quite annoying, for example, when writing SQL statements for a Base "Query" object.

Severity: undecided

The empty error message is ugly, but not the only one within Base, so that's nothing which will block an 1.0 release ... (Ulf) But why does it work fine with the JDBC driver?

=== Default values not properly processed ===

The Base table editor neither properly sets default values nor does it re-engineer default values properly.

Severity: 1.1

Again, this is a known issue. The default value displayed in the UI is a so-called "control default", which is applied to ''controls'' used to enter data into the given field. The DB-side default for a column is a different property, API-wise, and currently not evaluated at all. Probably not even properly fetched by most existing drivers.

Changing this is possible, but probably requires UI changes. First, we would need to define how the control default and the DB default should interact in the UI. A possible scenario would be to drop the UI support for the control default, and always use the DB default (even in controls), as long as the driver supports providing/accepting DB defaults.

=== BIGINT values crippled ===

Large BIGINT values are displayed in Base using scientific notation: 1e+15. If one changes the display format to number #.### the first 14 values of a large number (9223372036854775807) are displayed properly but then some rounding takes place, for example: 9223372036854800000. Connector/C++ can handle long long (L64) values properly and Base does use getLong() nevertheless the displayed value seems wrong.

Severity: undecided

I bet that's because of the number formatter ... processing numbers for display is done using a office-wide number formatter component. Unfortunately, it works with double-precision values only, which imposes a precision loss for certain values. This applies to "too-large" values, as well as fractional values with "too many" digits. This is a general problem in Base, and not limited to the MySQL Native Driver.

A possible solution would be to '''not'' employ the number formatter for certain column types. (Effectively, this means ''not'' using a <code>FormattedField</code> for the respective table column in the data view, but a NumericField, which internally works with long integer values of arbitrary (?) length.) This would solve the BIGINT issue, though not the too-many-digits issue for fractional values.

=== Tools -> User Administration does not work ===

When you choose <code>Tools/User administration...</code>, you're presented with an error.

Severity: required (remove the menu item)

Severity: required (implement proper user administration)

=== create table with wizard fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

run table wizard: take default & all field & push finish → java assertion list appears

Severity: required

Reason: unknown

=== change pk fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

open table with pk and change pk to any other field -> error: duplicate entry for key

Severity: required

Reason: pk not detected?

=== change table fieldtype in edit view not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

open table in edit mode -> fieldtypes greyed out (not possible to change)

Severity: required

Reason: The driver does not support <code>XAlterTable</code> (and more SDBCX-level interfaces)

=== fieldtype is changed after saving ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

in table edit view: create a field from f.e. type bool & save → tinyint

Severity: required

Reason: maybe the same problem like 1.10 & 1.11

(Ulf) Duplicate and not an error in C/C++. There is no boolean type in MySQL. However, its handled in the JDBC driver case, the best we can do is emulate it in the same way.

=== copy table & paste special fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

copy table & paste special (change tablename) with pk → invalid error message without text appears

Severity: required

Reason: unknown

=== query wizard shows 'query' as 'table' ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

create any query, open query wizard → tables listbox propose query (also with the other wizards)

Severity: required

Reason: unknown

== Developer Observations ==

This section collects observations interesting for developers only. It's likely the describe the root cause for another problem listed in the ''End User Observations'' section. In this sense, they might be duplicates, but we currently just use this as reminder list whenever we notice a problem ...

=== Do we need any of those? ===

ERROR: SQL Exception ODatabaseMetaData::getCrossReference: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getProcedures: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getUDTs: feature not implemented.
ERROR: SQL exception ODatabaseMetaData::supportsIntegrityEnhancementFacility: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::supportsResultSetConcurrency: feature not implemented.

=== INSERT does not work ===

Inserting data into a simple table does not work. Works fine when using the JDBC driver.

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Severity: required

=== information_schema (I_S) not shown in schema list ===

SHOW DATABASES shows the I_S. When quering the I_S for schema, the I_S will not expose itself. Different versions of Connector/C++ use different ways to fetch schema lists. Until and including Alpha SHOW DATABSES is used.

When using the JDBC driver and specifying no database in the connection URL no schemata are shown at all.

Severity: undecided

=== DatabseMetaData::getColumns() COLUMN_SIZE ===

DatabseMetaData::getColumns() takes COLUMN_SIZE from getDisplaySize().

Affected: DECIMAL/FLOAT.

Severity: required

Note: DisplaySize is not the same as ColumnSize. The former is a hint for UI processors which are to display the data in a tabular way. Currently, Base does not make use of this attribute.
The ColumnSize's semantics is described in the [http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String) Java API], and Base uses it in the very same semantics.
As a consequence, COLUMN_SIZE is what needs to be tweaked.

=== DatabseMetaData::getColumns() DECIMAL_DIGITS ===

DatabseMetaData::getColumns() does not set DECIMAL_DIGITS. Therefore, Base does not show it properly.

=== Perfoemance problem when accessing big tables ===

Open a table with more then 1000 rows. Jump to last one. => 2 min.

Severity: required

== Potential Issues ==

This section serves as collection of issues which might become a problem to end users, though we did not yet (bother to) create scenarios where users are hit by those (potential) problems.

=== TIME value range ===

[http://dev.mysql.com/doc/refman/5.1/en/time.html|MySQL's TIME] data type may have a significantly larger value range than the Base counterpart.

Severity: undecided

=== TINYINT / BOOLEAN ===

Educate Base users on [http://dev.mysql.com/doc/refman/5.1/en/other-vendor-data-types.html MySQL Server type mappings], for example BOOL[EAN] -> TINYINT.

== fixed ==

=== Tools -> Relations... not working ===

Error message: Database not support relations.

We should hint MySQL users in the driver documentation that Base takes no(?) measures to clean up no longer needed indexes. MySQL's InnoDB needs some special treatment.

Severity: required

With 3.x, Base is able to administrate MySQL's relationships (via the ODBC/JDBC bridge), so the native driver should be able to do this, too. At least with approximately the same set of bugs as the "old" driver :)

=== insert data in table not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

create any table with pk → not possible to insert data into table

Severity: required

Investigation: The driver currently returns an empty result set when being asked for the table privileges: <code>getTablePrivileges( null, "schema", "table" )</code>. Debugging deeper seems to indicate that parsing the result of a "SHOW GRANTS" query is flawed.

=== Tools->SQL does not show error message ===

reported by Ulf on 08/01/2009

Open the SQL execution wizard by invoking Tools->SQL. Run an invalid SQL query, for example, "create table foo". Base prints a new line "n:" in the status part of the window but it shows no error message.

Severity: required

=== New tables shown after "refresh tables" but (delete) rights/grants wrong? ===

reported by Ulf on 08/01/2009

Create some tables in MySQL. Start Base and browse the table list. Create a new table in MySQL (not in Base!), make sure it has a PK, add some records. Select View->Refresh tables. Base will show the new table. Try to remove a row from the newly created table. Base rejects the delete operation stating that the user as insufficient rights.

Investigation: This is a general problem currently, <code>DatabaseMetaData::getTablePrivileges</code> returns wrong data (all the time? sometimes? andrey claimed to have fixed this, but the fix does not work for me). If I fake the getTablePrivileges implementation to return the full set of privileges regardless the table being asked for, then the problem does not happen.

=== DECIMAL shown as TEXT ===

Base shows numerical DECIMAL columns as TEXT (in the table editor?).

Severity: required

Investigation: column is reported as <code>MYSQL_TYPE_NEWDECIMAL</code>, which wasn't covered in C/OOo (which only had a case for <code>MYSQL_TYPE_DECIMAL</code>)
=== Subforms do not work ===

Well, some of them do ... more precisely, SQL statements with named parameters (":param_name") do not work in general. The ODBC/JDBC driver wrapper used to replace them with unnamed parameters ("?"), 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.

Severity: required

Fixing this should be easy, at least so it is as usable as with other DBs/drivers, in particular with the existing MySQL-(O/J)DBC bridge. Before sending statements to the server, the driver must replace (unless the statement's <code>EscapeProcessing</code> is <code>FALSE</code>, of course) named parameters with anonymous ones. The disadvantage is that this only works when Base itself can parse the statement, and that it potentially changes the statement. However, both statements are true for all other DBs which do not support named parameters, too.

Database/Drivers/MySQL Native/Known Problems

2009-01-23T10:37:34Z

Oj: /* End User Observations */

{{DISPLAYTITLE:MySQL Native Driver: Known Problems}}

This page lists the currently known problems with the MySQL Native Driver, aka MySQL Connector/OOo.

== End User Observations ==

This section collects issues as observed by end users

=== Template for new entries ===

reported by NAME on xx/01/2009 - needs review

Description goes here.

Severity: undecided

Reason: unknown

=== Copying tables may not work properly ===

reported by NAME on xx/01/2009 - needs review

'''Needs further and systematic testing!'''

Original table:

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
`col2` char(1) default NULL,
`col3` varchar(50) default NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`),
KEY `idx_col2` (`col2`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Copy:

CREATE TABLE `source2` (
`id` int(10) NOT NULL,
`col1` int(10) default NULL,
`col2` char(3) default NULL,
`col3` varchar(150) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

* Wrong column definitions (known issue)
* NOT NULL not properly handled
* Index information not copyied (same with JDBC, might be a Base issue)

Severity: undecided

Reason: unknown

=== Wrong column width reported for text/binary columns ===

reported by Ulf on 09/01/2009 - needs review

We discussed this before and it might be fixed in the current source, but I work on an older snapshot. We return number of bytes, OO.org wants number of characters. A typical follow-up error is that copying tables may fail and/or give wrong results.

From an earlier mail exchange:

Hintergrund: für eine VARBINARY(10)-Spalte in MySQL liefern wir aktuell
40, für eine INTEGER-Spalte in MySQL liefern wir aktuell 11. Wir liefern
momentan 40 für VARBINARY(10), weil das Feld maximal 10 Zeichen aufnehmen kann, die maximal 4 Bytes für das Encoding benötigen. Für ein VARCHAR(255) wird sogar VARCHAR(255) der Wert von 3060 geliefert, weil hier der MySQL Server nochmal in einem seiner Datenfelder einen Mul tiplikator von 3 einbaut (255 * 3 * 4 = 3060).

And:

Später am Abend fiel es mir wieder ein... wir ziehen getColumnDisplaySize() intern im Connector/C++ ran für ConnectionMetaData::getColumns() -> COLUMN_SIZE.
rs_data.push_back(my_i_to_a(buf, sizeof(buf)-1, (long) rs3_meta->getColumnDisplaySize(i))); // Column size

Severity: required

Reason: unknown

=== Renaming a view not possible ===

reported by Ulf on 09/01/2009 - needs review

Tested with the native driver: Its not possible to rename a view, the UI does not offer the context menu item when selecting the view in the table list.

Severity: desired

Reason: missing SDBCX support of the driver. In general, tables can only be renamed when there is a css.sdbcx.Table object representing a single table, which supports the XRename interface.

=== (JDBC) Renaming a view "makes" it a table ===

reported by Ulf on 09/01/2009 - needs review

Tested with the JDBC driver. Create a view and rename it in Base. Base changes the icon in the table list and shows the renamed object as a table :-)

Severity: low

Reason: unknown

=== Removing records from views fails ===

reported by Ulf on 08/01/2009

Removing records from SQL views neither works with the JDBC driver nor with the native driver. Base sends a misformed query like: "DELETE FROM `test`.`v` W"

Severity: low

Reason: Removing records from views is in general not possible in Base. The fact that "Edit/Delete record" is enabled for a view (as in any table which the user does not have the DELETE privilege for) is a bug, which I fixed in the CWS.

=== Empty schemata not shown ===

Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown.

Severity: desired

Reason: OOo calls getTables() - no tables - schema not displayed. Setting might even be cached - verify that database becomes visible after creating table (from mysql prompt) in schema.

=== SMALLINT shown as REAL ===

When loading a table with a SMALLINT column it is shown as a FLOAT/REAL column in Base (in the table editor?)

Severity: required

=== OOo shows unrelated databases/schemata ===

Create a new Base database that connects to a MySQL schemata "test". Have "test" in the connection settings! OOo will ignore it and query MySQL for all tables in all schematas, and also display all those tables.

As a consequence the user will see all schemata he has access to not only the schemata/database "test" as requested in the connection settings

Severity: desired

=== No default schema on table creation ===

Base does not preselect a default schema in the table editor dialog. Its does not even if you connect to a certain schema by specifying it in the connection settings.

Severity: desired

=== No way to set MySQL specific table attributes ===

The Base table editor does not give access to table attributes. Not even basic ones such as the Engine (MyISAM: non-transactional, InnoDB: transactional).

Severity: 1.1

=== Base does not recognize schema changes ===

After connecting to a database and opening a table once, Base will not recognize changes applied to the DB schema meanwhile when opening the table in the table editor again.

Severity: low

that's not nice, but consistent with other DB/Drivers. For this purpose, there's View/Refresh Tables ...

=== Table column comments not synced between MySQL and Base ===

Base table column comments are not synchronized with the MySQL DB and its schema. Existing comments are not displayed in Base, and entering comments in the table editor is not propagated to MySQL.

Severity: later

That's a known issue with all database types. The column description as displayed in Base is purely client-side, and stored within the .odb file only. There's also an issue for this, but I'm too lazy too search for it right now ...

=== Violation of FK constraint gives two errors instead of one ===

Create two tables. Have one table "derived" reference entries in the other table "source". Try to remove a referenced record from the table "source". MySQL will report an error stating that you are violating a FK constrain. When using the MySQL JDBC driver the Base shows one requester with stating something like "Error - (error message from MySQL)". When using the native driver you get an requester stating "error" and you can proceed to an error details dialog. In the details dialog you will find two errors. The first has no message, the second shows the error message provided by MySQL.

This is a common pattern. Cause any SQL error and you can see up to three errors when you quit the initial requester using the button "more". Quite annoying, for example, when writing SQL statements for a Base "Query" object.

Severity: undecided

The empty error message is ugly, but not the only one within Base, so that's nothing which will block an 1.0 release ... (Ulf) But why does it work fine with the JDBC driver?

=== Default values not properly processed ===

The Base table editor neither properly sets default values nor does it re-engineer default values properly.

Severity: 1.1

Again, this is a known issue. The default value displayed in the UI is a so-called "control default", which is applied to ''controls'' used to enter data into the given field. The DB-side default for a column is a different property, API-wise, and currently not evaluated at all. Probably not even properly fetched by most existing drivers.

Changing this is possible, but probably requires UI changes. First, we would need to define how the control default and the DB default should interact in the UI. A possible scenario would be to drop the UI support for the control default, and always use the DB default (even in controls), as long as the driver supports providing/accepting DB defaults.

=== BIGINT values crippled ===

Large BIGINT values are displayed in Base using scientific notation: 1e+15. If one changes the display format to number #.### the first 14 values of a large number (9223372036854775807) are displayed properly but then some rounding takes place, for example: 9223372036854800000. Connector/C++ can handle long long (L64) values properly and Base does use getLong() nevertheless the displayed value seems wrong.

Severity: undecided

I bet that's because of the number formatter ... processing numbers for display is done using a office-wide number formatter component. Unfortunately, it works with double-precision values only, which imposes a precision loss for certain values. This applies to "too-large" values, as well as fractional values with "too many" digits. This is a general problem in Base, and not limited to the MySQL Native Driver.

A possible solution would be to '''not'' employ the number formatter for certain column types. (Effectively, this means ''not'' using a <code>FormattedField</code> for the respective table column in the data view, but a NumericField, which internally works with long integer values of arbitrary (?) length.) This would solve the BIGINT issue, though not the too-many-digits issue for fractional values.

=== Tools -> User Administration does not work ===

When you choose <code>Tools/User administration...</code>, you're presented with an error.

Severity: required (remove the menu item)

Severity: required (implement proper user administration)

=== create table with wizard fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

run table wizard: take default & all field & push finish → java assertion list appears

Severity: required

Reason: unknown

=== change pk fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

open table with pk and change pk to any other field -> error: duplicate entry for key

Severity: required

Reason: pk not detected?

=== change table fieldtype in edit view not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

open table in edit mode -> fieldtypes greyed out (not possible to change)

Severity: required

Reason: The driver does not support <code>XAlterTable</code> (and more SDBCX-level interfaces)

=== fieldtype is changed after saving ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

in table edit view: create a field from f.e. type bool & save → tinyint

Severity: required

Reason: maybe the same problem like 1.10 & 1.11

(Ulf) Duplicate and not an error in C/C++. There is no boolean type in MySQL. However, its handled in the JDBC driver case, the best we can do is emulate it in the same way.

=== copy table & paste special fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

copy table & paste special (change tablename) with pk → invalid error message without text appears

Severity: required

Reason: unknown

=== query wizard shows 'query' as 'table' ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

create any query, open query wizard → tables listbox propose query (also with the other wizards)

Severity: required

Reason: unknown

== Developer Observations ==

This section collects observations interesting for developers only. It's likely the describe the root cause for another problem listed in the ''End User Observations'' section. In this sense, they might be duplicates, but we currently just use this as reminder list whenever we notice a problem ...

=== Do we need any of those? ===

ERROR: SQL Exception ODatabaseMetaData::getCrossReference: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getProcedures: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getUDTs: feature not implemented.
ERROR: SQL exception ODatabaseMetaData::supportsIntegrityEnhancementFacility: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::supportsResultSetConcurrency: feature not implemented.

=== INSERT does not work ===

Inserting data into a simple table does not work. Works fine when using the JDBC driver.

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Severity: required

=== information_schema (I_S) not shown in schema list ===

SHOW DATABASES shows the I_S. When quering the I_S for schema, the I_S will not expose itself. Different versions of Connector/C++ use different ways to fetch schema lists. Until and including Alpha SHOW DATABSES is used.

When using the JDBC driver and specifying no database in the connection URL no schemata are shown at all.

Severity: undecided

=== DatabseMetaData::getColumns() COLUMN_SIZE ===

DatabseMetaData::getColumns() takes COLUMN_SIZE from getDisplaySize().

Affected: DECIMAL/FLOAT.

Severity: required

Note: DisplaySize is not the same as ColumnSize. The former is a hint for UI processors which are to display the data in a tabular way. Currently, Base does not make use of this attribute.
The ColumnSize's semantics is described in the [http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String) Java API], and Base uses it in the very same semantics.
As a consequence, COLUMN_SIZE is what needs to be tweaked.

=== DatabseMetaData::getColumns() DECIMAL_DIGITS ===

DatabseMetaData::getColumns() does not set DECIMAL_DIGITS. Therefore, Base does not show it properly.

=== Perfoemance problem when accessing big tables ===

Open a table with more then 1000 rows. Jump to last one. => 2 min.

Severity: required

== Potential Issues ==

This section serves as collection of issues which might become a problem to end users, though we did not yet (bother to) create scenarios where users are hit by those (potential) problems.

=== TIME value range ===

[http://dev.mysql.com/doc/refman/5.1/en/time.html|MySQL's TIME] data type may have a significantly larger value range than the Base counterpart.

Severity: undecided

=== TINYINT / BOOLEAN ===

Educate Base users on [http://dev.mysql.com/doc/refman/5.1/en/other-vendor-data-types.html MySQL Server type mappings], for example BOOL[EAN] -> TINYINT.

== fixed ==

=== Tools -> Relations... not working ===

Error message: Database not support relations.

We should hint MySQL users in the driver documentation that Base takes no(?) measures to clean up no longer needed indexes. MySQL's InnoDB needs some special treatment.

Severity: required

With 3.x, Base is able to administrate MySQL's relationships (via the ODBC/JDBC bridge), so the native driver should be able to do this, too. At least with approximately the same set of bugs as the "old" driver :)

=== insert data in table not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

create any table with pk → not possible to insert data into table

Severity: required

Investigation: The driver currently returns an empty result set when being asked for the table privileges: <code>getTablePrivileges( null, "schema", "table" )</code>. Debugging deeper seems to indicate that parsing the result of a "SHOW GRANTS" query is flawed.

=== Tools->SQL does not show error message ===

reported by Ulf on 08/01/2009

Open the SQL execution wizard by invoking Tools->SQL. Run an invalid SQL query, for example, "create table foo". Base prints a new line "n:" in the status part of the window but it shows no error message.

Severity: required

=== New tables shown after "refresh tables" but (delete) rights/grants wrong? ===

reported by Ulf on 08/01/2009

Create some tables in MySQL. Start Base and browse the table list. Create a new table in MySQL (not in Base!), make sure it has a PK, add some records. Select View->Refresh tables. Base will show the new table. Try to remove a row from the newly created table. Base rejects the delete operation stating that the user as insufficient rights.

Investigation: This is a general problem currently, <code>DatabaseMetaData::getTablePrivileges</code> returns wrong data (all the time? sometimes? andrey claimed to have fixed this, but the fix does not work for me). If I fake the getTablePrivileges implementation to return the full set of privileges regardless the table being asked for, then the problem does not happen.

=== DECIMAL shown as TEXT ===

Base shows numerical DECIMAL columns as TEXT (in the table editor?).

Severity: required

Investigation: column is reported as <code>MYSQL_TYPE_NEWDECIMAL</code>, which wasn't covered in C/OOo (which only had a case for <code>MYSQL_TYPE_DECIMAL</code>)

Database/Drivers/MySQL Native/Known Problems

2009-01-23T10:27:01Z

Oj: /* Developer Observations */

{{DISPLAYTITLE:MySQL Native Driver: Known Problems}}

This page lists the currently known problems with the MySQL Native Driver, aka MySQL Connector/OOo.

== End User Observations ==

This section collects issues as observed by end users

=== Template for new entries ===

reported by NAME on xx/01/2009 - needs review

Description goes here.

Severity: undecided

Reason: unknown

=== Copying tables may not work properly ===

reported by NAME on xx/01/2009 - needs review

'''Needs further and systematic testing!'''

Original table:

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
`col2` char(1) default NULL,
`col3` varchar(50) default NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`),
KEY `idx_col2` (`col2`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Copy:

CREATE TABLE `source2` (
`id` int(10) NOT NULL,
`col1` int(10) default NULL,
`col2` char(3) default NULL,
`col3` varchar(150) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

* Wrong column definitions (known issue)
* NOT NULL not properly handled
* Index information not copyied (same with JDBC, might be a Base issue)

Severity: undecided

Reason: unknown

=== Wrong column width reported for text/binary columns ===

reported by Ulf on 09/01/2009 - needs review

We discussed this before and it might be fixed in the current source, but I work on an older snapshot. We return number of bytes, OO.org wants number of characters. A typical follow-up error is that copying tables may fail and/or give wrong results.

From an earlier mail exchange:

Hintergrund: für eine VARBINARY(10)-Spalte in MySQL liefern wir aktuell
40, für eine INTEGER-Spalte in MySQL liefern wir aktuell 11. Wir liefern
momentan 40 für VARBINARY(10), weil das Feld maximal 10 Zeichen aufnehmen kann, die maximal 4 Bytes für das Encoding benötigen. Für ein VARCHAR(255) wird sogar VARCHAR(255) der Wert von 3060 geliefert, weil hier der MySQL Server nochmal in einem seiner Datenfelder einen Mul tiplikator von 3 einbaut (255 * 3 * 4 = 3060).

And:

Später am Abend fiel es mir wieder ein... wir ziehen getColumnDisplaySize() intern im Connector/C++ ran für ConnectionMetaData::getColumns() -> COLUMN_SIZE.
rs_data.push_back(my_i_to_a(buf, sizeof(buf)-1, (long) rs3_meta->getColumnDisplaySize(i))); // Column size

Severity: required

Reason: unknown

=== Renaming a view not possible ===

reported by Ulf on 09/01/2009 - needs review

Tested with the native driver: Its not possible to rename a view, the UI does not offer the context menu item when selecting the view in the table list.

Severity: desired

Reason: missing SDBCX support of the driver. In general, tables can only be renamed when there is a css.sdbcx.Table object representing a single table, which supports the XRename interface.

=== (JDBC) Renaming a view "makes" it a table ===

reported by Ulf on 09/01/2009 - needs review

Tested with the JDBC driver. Create a view and rename it in Base. Base changes the icon in the table list and shows the renamed object as a table :-)

Severity: low

Reason: unknown

=== Removing records from views fails ===

reported by Ulf on 08/01/2009

Removing records from SQL views neither works with the JDBC driver nor with the native driver. Base sends a misformed query like: "DELETE FROM `test`.`v` W"

Severity: low

Reason: Removing records from views is in general not possible in Base. The fact that "Edit/Delete record" is enabled for a view (as in any table which the user does not have the DELETE privilege for) is a bug, which I fixed in the CWS.

=== Empty schemata not shown ===

Create an empty schemata/database. Create a new Base database which connects to an empty MySQL database. The MySQL database is not shown.

Severity: desired

Reason: OOo calls getTables() - no tables - schema not displayed. Setting might even be cached - verify that database becomes visible after creating table (from mysql prompt) in schema.

=== SMALLINT shown as REAL ===

When loading a table with a SMALLINT column it is shown as a FLOAT/REAL column in Base (in the table editor?)

Severity: required

=== OOo shows unrelated databases/schemata ===

Create a new Base database that connects to a MySQL schemata "test". Have "test" in the connection settings! OOo will ignore it and query MySQL for all tables in all schematas, and also display all those tables.

As a consequence the user will see all schemata he has access to not only the schemata/database "test" as requested in the connection settings

Severity: desired

=== No default schema on table creation ===

Base does not preselect a default schema in the table editor dialog. Its does not even if you connect to a certain schema by specifying it in the connection settings.

Severity: desired

=== No way to set MySQL specific table attributes ===

The Base table editor does not give access to table attributes. Not even basic ones such as the Engine (MyISAM: non-transactional, InnoDB: transactional).

Severity: 1.1

=== Base does not recognize schema changes ===

After connecting to a database and opening a table once, Base will not recognize changes applied to the DB schema meanwhile when opening the table in the table editor again.

Severity: low

that's not nice, but consistent with other DB/Drivers. For this purpose, there's View/Refresh Tables ...

=== Table column comments not synced between MySQL and Base ===

Base table column comments are not synchronized with the MySQL DB and its schema. Existing comments are not displayed in Base, and entering comments in the table editor is not propagated to MySQL.

Severity: later

That's a known issue with all database types. The column description as displayed in Base is purely client-side, and stored within the .odb file only. There's also an issue for this, but I'm too lazy too search for it right now ...

=== Violation of FK constraint gives two errors instead of one ===

Create two tables. Have one table "derived" reference entries in the other table "source". Try to remove a referenced record from the table "source". MySQL will report an error stating that you are violating a FK constrain. When using the MySQL JDBC driver the Base shows one requester with stating something like "Error - (error message from MySQL)". When using the native driver you get an requester stating "error" and you can proceed to an error details dialog. In the details dialog you will find two errors. The first has no message, the second shows the error message provided by MySQL.

This is a common pattern. Cause any SQL error and you can see up to three errors when you quit the initial requester using the button "more". Quite annoying, for example, when writing SQL statements for a Base "Query" object.

Severity: undecided

The empty error message is ugly, but not the only one within Base, so that's nothing which will block an 1.0 release ... (Ulf) But why does it work fine with the JDBC driver?

=== Default values not properly processed ===

The Base table editor neither properly sets default values nor does it re-engineer default values properly.

Severity: 1.1

Again, this is a known issue. The default value displayed in the UI is a so-called "control default", which is applied to ''controls'' used to enter data into the given field. The DB-side default for a column is a different property, API-wise, and currently not evaluated at all. Probably not even properly fetched by most existing drivers.

Changing this is possible, but probably requires UI changes. First, we would need to define how the control default and the DB default should interact in the UI. A possible scenario would be to drop the UI support for the control default, and always use the DB default (even in controls), as long as the driver supports providing/accepting DB defaults.

=== BIGINT values crippled ===

Large BIGINT values are displayed in Base using scientific notation: 1e+15. If one changes the display format to number #.### the first 14 values of a large number (9223372036854775807) are displayed properly but then some rounding takes place, for example: 9223372036854800000. Connector/C++ can handle long long (L64) values properly and Base does use getLong() nevertheless the displayed value seems wrong.

Severity: undecided

I bet that's because of the number formatter ... processing numbers for display is done using a office-wide number formatter component. Unfortunately, it works with double-precision values only, which imposes a precision loss for certain values. This applies to "too-large" values, as well as fractional values with "too many" digits. This is a general problem in Base, and not limited to the MySQL Native Driver.

A possible solution would be to '''not'' employ the number formatter for certain column types. (Effectively, this means ''not'' using a <code>FormattedField</code> for the respective table column in the data view, but a NumericField, which internally works with long integer values of arbitrary (?) length.) This would solve the BIGINT issue, though not the too-many-digits issue for fractional values.

=== Subforms do not work ===

Well, some of them do ... more precisely, SQL statements with named parameters (":param_name") do not work in general. The ODBC/JDBC driver wrapper used to replace them with unnamed parameters ("?"), 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.

Severity: required

Fixing this should be easy, at least so it is as usable as with other DBs/drivers, in particular with the existing MySQL-(O/J)DBC bridge. Before sending statements to the server, the driver must replace (unless the statement's <code>EscapeProcessing</code> is <code>FALSE</code>, of course) named parameters with anonymous ones. The disadvantage is that this only works when Base itself can parse the statement, and that it potentially changes the statement. However, both statements are true for all other DBs which do not support named parameters, too.

=== Tools -> User Administration does not work ===

When you choose <code>Tools/User administration...</code>, you're presented with an error.

Severity: required (remove the menu item)

Severity: required (implement proper user administration)

=== create table with wizard fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

run table wizard: take default & all field & push finish → java assertion list appears

Severity: required

Reason: unknown

=== change pk fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

open table with pk and change pk to any other field -> error: duplicate entry for key

Severity: required

Reason: pk not detected?

=== change table fieldtype in edit view not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

open table in edit mode -> fieldtypes greyed out (not possible to change)

Severity: required

Reason: The driver does not support <code>XAlterTable</code> (and more SDBCX-level interfaces)

=== fieldtype is changed after saving ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

in table edit view: create a field from f.e. type bool & save → tinyint

Severity: required

Reason: maybe the same problem like 1.10 & 1.11

(Ulf) Duplicate and not an error in C/C++. There is no boolean type in MySQL. However, its handled in the JDBC driver case, the best we can do is emulate it in the same way.

=== copy table & paste special fails ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

copy table & paste special (change tablename) with pk → invalid error message without text appears

Severity: required

Reason: unknown

=== query wizard shows 'query' as 'table' ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009 - needs review

create any query, open query wizard → tables listbox propose query (also with the other wizards)

Severity: required

Reason: unknown

== Developer Observations ==

This section collects observations interesting for developers only. It's likely the describe the root cause for another problem listed in the ''End User Observations'' section. In this sense, they might be duplicates, but we currently just use this as reminder list whenever we notice a problem ...

=== Do we need any of those? ===

ERROR: SQL Exception ODatabaseMetaData::getCrossReference: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getProcedures: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::getUDTs: feature not implemented.
ERROR: SQL exception ODatabaseMetaData::supportsIntegrityEnhancementFacility: feature not implemented.
ERROR: SQL Exception ODatabaseMetaData::supportsResultSetConcurrency: feature not implemented.

=== INSERT does not work ===

Inserting data into a simple table does not work. Works fine when using the JDBC driver.

CREATE TABLE `source` (
`id` int(11) NOT NULL,
`col1` int(11) NOT NULL,
PRIMARY KEY (`id`),
KEY `idx_col1` (`col1`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Severity: required

=== information_schema (I_S) not shown in schema list ===

SHOW DATABASES shows the I_S. When quering the I_S for schema, the I_S will not expose itself. Different versions of Connector/C++ use different ways to fetch schema lists. Until and including Alpha SHOW DATABSES is used.

When using the JDBC driver and specifying no database in the connection URL no schemata are shown at all.

Severity: undecided

=== DatabseMetaData::getColumns() COLUMN_SIZE ===

DatabseMetaData::getColumns() takes COLUMN_SIZE from getDisplaySize().

Affected: DECIMAL/FLOAT.

Severity: required

Note: DisplaySize is not the same as ColumnSize. The former is a hint for UI processors which are to display the data in a tabular way. Currently, Base does not make use of this attribute.
The ColumnSize's semantics is described in the [http://java.sun.com/javase/6/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String) Java API], and Base uses it in the very same semantics.
As a consequence, COLUMN_SIZE is what needs to be tweaked.

=== DatabseMetaData::getColumns() DECIMAL_DIGITS ===

DatabseMetaData::getColumns() does not set DECIMAL_DIGITS. Therefore, Base does not show it properly.

=== Perfoemance problem when accessing big tables ===

Open a table with more then 1000 rows. Jump to last one. => 2 min.

Severity: required

== Potential Issues ==

This section serves as collection of issues which might become a problem to end users, though we did not yet (bother to) create scenarios where users are hit by those (potential) problems.

=== TIME value range ===

[http://dev.mysql.com/doc/refman/5.1/en/time.html|MySQL's TIME] data type may have a significantly larger value range than the Base counterpart.

Severity: undecided

=== TINYINT / BOOLEAN ===

Educate Base users on [http://dev.mysql.com/doc/refman/5.1/en/other-vendor-data-types.html MySQL Server type mappings], for example BOOL[EAN] -> TINYINT.

== fixed ==

=== Tools -> Relations... not working ===

Error message: Database not support relations.

We should hint MySQL users in the driver documentation that Base takes no(?) measures to clean up no longer needed indexes. MySQL's InnoDB needs some special treatment.

Severity: required

With 3.x, Base is able to administrate MySQL's relationships (via the ODBC/JDBC bridge), so the native driver should be able to do this, too. At least with approximately the same set of bugs as the "old" driver :)

=== insert data in table not possible ===

reported by [http://wiki.services.openoffice.org/wiki/User:Clu CLU] on 12/01/2009

create any table with pk → not possible to insert data into table

Severity: required

Investigation: The driver currently returns an empty result set when being asked for the table privileges: <code>getTablePrivileges( null, "schema", "table" )</code>. Debugging deeper seems to indicate that parsing the result of a "SHOW GRANTS" query is flawed.

=== Tools->SQL does not show error message ===

reported by Ulf on 08/01/2009

Open the SQL execution wizard by invoking Tools->SQL. Run an invalid SQL query, for example, "create table foo". Base prints a new line "n:" in the status part of the window but it shows no error message.

Severity: required

=== New tables shown after "refresh tables" but (delete) rights/grants wrong? ===

reported by Ulf on 08/01/2009

Create some tables in MySQL. Start Base and browse the table list. Create a new table in MySQL (not in Base!), make sure it has a PK, add some records. Select View->Refresh tables. Base will show the new table. Try to remove a row from the newly created table. Base rejects the delete operation stating that the user as insufficient rights.

Investigation: This is a general problem currently, <code>DatabaseMetaData::getTablePrivileges</code> returns wrong data (all the time? sometimes? andrey claimed to have fixed this, but the fix does not work for me). If I fake the getTablePrivileges implementation to return the full set of privileges regardless the table being asked for, then the problem does not happen.

=== DECIMAL shown as TEXT ===

Base shows numerical DECIMAL columns as TEXT (in the table editor?).

Severity: required

Investigation: column is reported as <code>MYSQL_TYPE_NEWDECIMAL</code>, which wasn't covered in C/OOo (which only had a case for <code>MYSQL_TYPE_DECIMAL</code>)

SUN Report Builder/Functions

2008-12-15T13:48:11Z

Oj: /* The Sun Report Builder supplies the following functions: */

{{Database/Lang|Base/Reports/Functions}}

'''Date/Time''' 
{| class="prettytable" cellpadding="10" border="1"
| '''''Function Name'''''
| '''''Description'''''
| '''''Example '''''

|-
| DATE
| Provides an internal number for the date given.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| month
| An integer between 1 and 12 representing the month.
|-
| day
| An integer between 1 and 31 representing the day of the month.
|}

|

|-
| DATEDIF
| Returns the number of years, months, or days between two dates.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| EndDate
| Second date.
|-
| Format
| Format code.
|}

|

|-
| DATEVALUE
| Returns an internal number for a text having a possible date format.
|

|-
| DAY
| Returns the sequential date of the month as an integer (1-31) in relation to the date value.
|

|-
| DAYS
| Calculates the number of days between two dates.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| Date_1
| The start date for calculating the difference in days.
|}

|

|-
| HOUR
| Determines the sequential number of the hour of the day (0-23) for the time value.
|

|-
| MINUTE
| Determines the sequential number for the minute of the hour (0-59) for the time value.
|

|-
| MONTH
| Determines the sequential number of a month of the year (1-12) for the date value.
|

|-
| NOW
| Determines the current time of the computer.
|

|-
| SECOND
| Determines the sequential number of the second of a minute (0-59) for the time value.
|

|-
| TIME
| Determines a time value from the details for hour, minute and second.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| minute
| The integer for the minute.
|-
| second
| The integer for the second.
|}

|

|-
| TIMEVALUE
| Returns a sequential number for a text shown in a possible time entry format.
|

|-
| TODAY
| Determines the current date of the computer.
|

|-
| WEEKDAY
| Returns the day of the week for the date value as an integer (1-7).
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| Type
| Fixes the beginning of the week and the type of calculation to be used.(1 = Sunday is the first day of the week, with value 1; Saturday has value 7, 2 = Monday is the first day of the week, with value 1; Sunday has value 7, 3 = Monday is the first day of the week, with value 0; Sunday has value 6)
|}

|

|-
| YEAR
| Returns the year of a date value as an integer.
|
|}
 
'''Mathematical''' 
{| class="prettytable" cellpadding="10" border="1"
| '''''Function Name'''''
| '''''Description'''''
| '''''Example '''''

|-
| ABS
| Absolute value of a number.
|

|-
| AVERAGE
| Returns the average of a sample.
|

|-
| AVERAGE
| Returns the average of a sample.
|

|-
| EVEN
| Rounds a positive number up and negative number down to the nearest even integer.
|

|-
| MAX
| Returns the maximum value in a list of arguments.
|

|-
| MAXA
| Returns the maximum value in a list of arguments. Text is evaluated as zero.
|

|-
| MIN
| Returns the minimum value in a list of arguments.
|

|-
| MINA
| Returns the smallest value in a list of arguments. Text is evaluated as zero.
|

|-
| MOD
| Calculates the remainder of a division.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| Divisor
| The number by which the dividend is divided.
|}

|

|-
| ODD
| Rounds a positive number up and negative number down to the nearest odd integer.
|

|-
| SUM
| Returns the sum of all arguments.
|
|}
 
'''Logical''' 
{| class="prettytable" cellpadding="10" border="1"
| '''''Function Name'''''
| '''''Description'''''
| '''''Example '''''

|-
| AND
| Returns TRUE if all arguments are TRUE.
|

|-
| FALSE
| Defines the logical value as FALSE.
|

|-
| IF
| Specifies a logical test to be performed.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| Then_value
| The result of the function if the logical test returns a TRUE.
|-
| Otherwise_value
| The result of the function if the logical test returns FALSE.
|}

|

|-
| NOT
| Reverses the value of the argument.
|

|-
| OR
| Returns TRUE if an argument is TRUE.
|

|-
| TRUE
| Returns the logical value TRUE.
|

|-
| XOR
| Returns TRUE if a odd number of arguments are TRUE.
|
|}
 
'''Information''' 
{| class="prettytable" cellpadding="10" border="1"
| '''''Function Name'''''
| '''''Description'''''
| '''''Example '''''

|-
| CHOOSE
| Selects a value from a list of up to 30 value arguments.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| value
| Value 1, value 2,... The list of arguments from which a value is chosen.
|}

|

|-
| COUNT
| Counts how many numbers are in the list of arguments.
|

|-
| COUNTA
| Counts how many values are in the list of arguments.
|

|-
| COUNTBLANK
| Counts the blank cells in a specified range.
|

|-
| HASCHANGED
| Checks whether the columns specified by the given names has changed.
|

|-
| ISBLANK
| Returns TRUE if value refers to an empty cell.
|

|-
| ISERR
| Returns TRUE if the value is an error value not equal to #N/A.
|

|-
| ISERROR
| Returns TRUE if the value is an error value.
|

|-
| ISEVEN
| Returns TRUE if value is an even integer.
|

|-
| ISLOGICAL
| Returns TRUE if the value carries a logical number format.
|

|-
| ISNA
| Returns TRUE if value equals #N/A.
|

|-
| ISNONTEXT
| Returns TRUE if the value is not text.
|

|-
| ISNUMBER
| Returns TRUE if value is a number.
|

|-
| ISODD
| Returns TRUE if value is an odd integer.
|

|-
| ISREF
| Returns TRUE if value is a reference.
|

|-
| ISTEXT
| Returns TRUE if value is text.
|

|-
| NA
| Not available. Returns the error value #N/A.
|
|}
 
'''User-Defined''' 
{| class="prettytable" cellpadding="10" border="1"
| '''''Function Name'''''
| '''''Description'''''
| '''''Example '''''

|-
| NULL
| Returns a NULL-Value
|
|}
 
'''Text''' 
{| class="prettytable" cellpadding="10" border="1"
| '''''Function Name'''''
| '''''Description'''''
| '''''Example '''''

|-
| EXACT
| Specifies whether two texts are identical.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| text_2
| The second text for comparing texts.
|}

|

|-
| FIND
| Looks for a string of text within another (case sensitive)
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| text
| The text in which a search is to be made.
|-
| position
| The position in the text from which the search starts.
|}

|

|-
| LEFT
| Returns the first character or characters of a text.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| number
| The number of characters for the start text.
|}

|

|-
| LEN
| Calculates length of a text string.
|

|-
| LOWER
| Converts text to lowercase.
|

|-
| MID
| Returns a partial text string of a text.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| start
| The position from which the part word is to be determined.
|-
| number
| The number of characters for the text.
|}

|

|-
| REPLACE
| Replaces characters within a text string with a different text string.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| position
| The character position from which text is to be replaced.
|-
| length
| The number of characters to be replaced.
|-
| new text
| The text to be inserted.
|}

|

|-
| REPT
| Repeats text a given number of times.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| number
| The number of times the text is to be repeated.
|}

|

|-
| RIGHT
| Returns the last character or characters of a text.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| number
| The number of characters for the end text.
|}

|

|-
| SUBSTITUTE
| Substitutes new text for old text in a string.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| search_text
| The partial string to be (repeatedly) replaced.
|-
| new text
| The text which is to replace the text string.
|-
| occurrence
| Which occurence of the old text is to be replaced.
|}

|

|-
| T
| Converts a value into text.
|

|-
| TEXT
| Converts a number to text according to a given format.
|

|-
| TRIM
| Removes extra spaces from text.
|

|-
| UNICHAR
| Converts a code number into a Unicode character or letter.
|

|-
| UNICODE
| Returns the numeric code for the first Unicode character in a text string.
|

|-
| UPPER
| Converts text to uppercase.
|

|-
| URLENCODE
| Applies URL-Encoding to a text given in the first parameter using the encoding specified in the second parameter. If no encoding is given, ISO-8859-1 is assumed.
{| class="prettytable" cellpadding="10" border="1"
| '''''Parameter Name'''''
| '''''Parameter Description'''''

|-
| Encoding
| The Encoding to be used.
|}

|
|}
 
'''Rounding''' 
{| class="prettytable" cellpadding="10" border="1"
| '''''Function Name'''''
| '''''Description'''''
| '''''Example '''''

|-
| INT
| Rounds a number down to the nearest integer.
|
|}

SUN Report Builder/Usability

2008-12-01T11:37:36Z

Oj: /* 2008-12-01 */

{{DISPLAYTITLE:Sun Report Builder Usability Issues}}
This is a collection of usability issues found with the Sun Report Builder extension. Usually, they should be put into IssueZilla issues, and low hanging fruits should be fixed ASAP.

__TOC__

== iTeam Meetings ==
=== 2008-12-01 ===
{| cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 1em;" border="1" rules="all"
|- align="left" style="background-color:#cccccc"
| '''Issue/Problem''' || style="width:3ex" | '''Status'''
|- align="left" style="background-color:#eeeeee"
| colspan="2" |''Add Field window''
|-
| When dragging entries to the document, both created controls should have an equal width. Otherwise, it's pretty inconvenient to create and modify/maintain a tabular structure in the report.
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f i96431]
|-
| Currently table fields are sorted like they appear in the table definition, but sometimes reversed/alphabetical sorting is desirable. Should have buttons (toolbar?) for doing so
| style="background-color:#c0ffc0; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96517 i96517]
|-
| when no section is active, double-clicking an entry (or pressing enter) does nothing. Should put into the Detail section by default.
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f i96431]
|-
| There should be a help text at the bottom of the window, stating something like "Double-click onto an column name, or drag and drop it into the document, to create a field displaying this column's data."
| style="background-color:#f0ee00; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96519 i96519]
|-
| There should be a button "Insert" at the bottom of the window, which does the same as double-clicking / DnD'ing an entry. This would make it more obvious to the user what is needed.
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Ffrmdlg i96520]
|-
| Drag and drop of multiple fields to the report is not possible. As soon as you click onto the multi-selection to start dragging, it is reverted to a single selection. Doing the same via pressing the enter key works as expected, though.
| style="background-color:#c0ffc0; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96522 i96522]
|- align="left" style="background-color:#eeeeee"
| colspan="2" |''Property Browser''
|-
| selecting an entry from a combo box'es drop down list by mouse should immediately activate this change. Currently, you still need to move the focus out of the combo box, which is silly.
| style="background-color:#f0ee00; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96429 i96429]
|-
| opening a new report should already fill in the first found table (if any) into the "Content" field of the property browser, so the report is already bound to this table. This gives the user a better clue what's needed, since the "Add Field" window will also immediately be open, listing all the fields of the table.
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f i96431]
|- align="left" style="background-color:#eeeeee"
| colspan="2" |''Miscellaneous''
|-
| Controls in the design should show a placeholder text, indicating the data source of this control. That is, if a control is bound to, say, table column "City", then a gray placeholder text "=City" should be drawn in the control.
| style="background-color:#f0ee00; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96523 i96523]
|-
| There are situations where marking multiple fields does not update the various alignment buttons in the toolbars - they stay disabled.
| style="background-color:#f0ee00; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96431 i96431]
|-
| multi-selection of controls in the design is too slow. Adding a new control to an existing selection can take multiple seconds.
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f i96431]
|-
| Why isn't the "Report Output Format" (found in the "File" menu, which is strange in itself) a property in the property browser?
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f i96431]
|- align="left" style="background-color:#eeeeee"
| colspan="2" |''Spreadsheet Reports''
|-
| The "Wrap text automatically" option for cells should automatically be set when we generate a spreadsheet document. Also, all rows should have the "Optimal row height" flag set. This way, we would have a reports where the cells automatically grow with their content.
| style="background-color:#f0ee00; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96524 i96524]
|- align="left" style="background-color:#eeeeee"
| colspan="2" |''Text Reports''
|-
| When a text does not fit into a table cell, there is *no* indication of this in the printout. While the screen display shows a red triangle as indication, but this is completely lost in the printout.
| style="background-color:#c0c0ff; text-align:center" | open
|-
| When a text does not fit into a table cell, then only the *words* which fit are printed. That is, if you have a text like "Sun Microsystems", where only "Sun Microsyst" would fit into the cell, then actually only "Sun" is displayed. It would be much better to not stop at word boundaries here, but instead display as much text as possible.
| style="background-color:#c0c0ff; text-align:center" | open
|}

'''Status legend'''
{| cellpadding="4" cellspacing="0" border="1" rules="all"
| style="background-color:#c0c0ff; text-align:center" | open
| problem is reported here, but not fixed, not even submitted in IssueZilla
|-
| style="background-color:#f0ee00; text-align:center" | i12345
| problem submitted in IssueZilla, with issue number indicated by the text
|-
| style="background-color:#c0ffc0; text-align:center" | i12345
| problem fixed in CWS linked to, with issue number indicated by the text
|}

[[Category:Sun Report Builder]]

SUN Report Builder/Usability

2008-12-01T11:37:08Z

Oj: /* 2008-11-17 */

{{DISPLAYTITLE:Sun Report Builder Usability Issues}}
This is a collection of usability issues found with the Sun Report Builder extension. Usually, they should be put into IssueZilla issues, and low hanging fruits should be fixed ASAP.

__TOC__

== iTeam Meetings ==
=== 2008-11-17 ===
{| cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 1em;" border="1" rules="all"
|- align="left" style="background-color:#cccccc"
| '''Issue/Problem''' || style="width:3ex" | '''Status'''
|- align="left" style="background-color:#eeeeee"
| colspan="2" |''Add Field window''
|-
| When dragging entries to the document, both created controls should have an equal width. Otherwise, it's pretty inconvenient to create and modify/maintain a tabular structure in the report.
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f i96431]
|-
| Currently table fields are sorted like they appear in the table definition, but sometimes reversed/alphabetical sorting is desirable. Should have buttons (toolbar?) for doing so
| style="background-color:#c0ffc0; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96517 i96517]
|-
| when no section is active, double-clicking an entry (or pressing enter) does nothing. Should put into the Detail section by default.
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f i96431]
|-
| There should be a help text at the bottom of the window, stating something like "Double-click onto an column name, or drag and drop it into the document, to create a field displaying this column's data."
| style="background-color:#f0ee00; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96519 i96519]
|-
| There should be a button "Insert" at the bottom of the window, which does the same as double-clicking / DnD'ing an entry. This would make it more obvious to the user what is needed.
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Ffrmdlg i96520]
|-
| Drag and drop of multiple fields to the report is not possible. As soon as you click onto the multi-selection to start dragging, it is reverted to a single selection. Doing the same via pressing the enter key works as expected, though.
| style="background-color:#c0ffc0; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96522 i96522]
|- align="left" style="background-color:#eeeeee"
| colspan="2" |''Property Browser''
|-
| selecting an entry from a combo box'es drop down list by mouse should immediately activate this change. Currently, you still need to move the focus out of the combo box, which is silly.
| style="background-color:#f0ee00; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96429 i96429]
|-
| opening a new report should already fill in the first found table (if any) into the "Content" field of the property browser, so the report is already bound to this table. This gives the user a better clue what's needed, since the "Add Field" window will also immediately be open, listing all the fields of the table.
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f i96431]
|- align="left" style="background-color:#eeeeee"
| colspan="2" |''Miscellaneous''
|-
| Controls in the design should show a placeholder text, indicating the data source of this control. That is, if a control is bound to, say, table column "City", then a gray placeholder text "=City" should be drawn in the control.
| style="background-color:#f0ee00; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96523 i96523]
|-
| There are situations where marking multiple fields does not update the various alignment buttons in the toolbars - they stay disabled.
| style="background-color:#f0ee00; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96431 i96431]
|-
| multi-selection of controls in the design is too slow. Adding a new control to an existing selection can take multiple seconds.
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f i96431]
|-
| Why isn't the "Report Output Format" (found in the "File" menu, which is strange in itself) a property in the property browser?
| style="background-color:#c0ffc0; text-align:center" | [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f i96431]
|- align="left" style="background-color:#eeeeee"
| colspan="2" |''Spreadsheet Reports''
|-
| The "Wrap text automatically" option for cells should automatically be set when we generate a spreadsheet document. Also, all rows should have the "Optimal row height" flag set. This way, we would have a reports where the cells automatically grow with their content.
| style="background-color:#f0ee00; text-align:center" | [http://www.openoffice.org/issues/show_bug.cgi?id=96524 i96524]
|- align="left" style="background-color:#eeeeee"
| colspan="2" |''Text Reports''
|-
| When a text does not fit into a table cell, there is *no* indication of this in the printout. While the screen display shows a red triangle as indication, but this is completely lost in the printout.
| style="background-color:#c0c0ff; text-align:center" | open
|-
| When a text does not fit into a table cell, then only the *words* which fit are printed. That is, if you have a text like "Sun Microsystems", where only "Sun Microsyst" would fit into the cell, then actually only "Sun" is displayed. It would be much better to not stop at word boundaries here, but instead display as much text as possible.
| style="background-color:#c0c0ff; text-align:center" | open
|}

'''Status legend'''
{| cellpadding="4" cellspacing="0" border="1" rules="all"
| style="background-color:#c0c0ff; text-align:center" | open
| problem is reported here, but not fixed, not even submitted in IssueZilla
|-
| style="background-color:#f0ee00; text-align:center" | i12345
| problem submitted in IssueZilla, with issue number indicated by the text
|-
| style="background-color:#c0ffc0; text-align:center" | i12345
| problem fixed in CWS linked to, with issue number indicated by the text
|}

[[Category:Sun Report Builder]]