Difference between revisions of "HSQLDB Integration"
From Apache OpenOffice Wiki
Timarandras (Talk | contribs) m (Category Development) |
(→Desired Features) |
||
| Line 12: | Line 12: | ||
== Desired Features == | == Desired Features == | ||
| − | |||
* single-file<br/>This would allow to get rid of the temporary files which are currently needed when working on the embedded HSQLDB, and thus remove some performance penalties | * single-file<br/>This would allow to get rid of the temporary files which are currently needed when working on the embedded HSQLDB, and thus remove some performance penalties | ||
[[Category:Development]] | [[Category:Development]] | ||
| + | * separation of the "auto increment" from the "primary key" concept. Currently, if you declare a column to be an auto increment column, it inevidentely becomes the primary key | ||
Revision as of 07:36, 4 May 2006
This is a (more technically orientated) page about the integration of the HSQLDB engine[1] into OpenOffice.org.
Things To Do
- localize error messages (currently all hard-coded English)
- get rid of the "default_schema=true" parameter?
OpenOffice.org-specific settings
Connection settings which are currently necessary to connect to HSQLDB embedded in an OpenOffice.org database file
- storage_key: unique key which globally identifies the connection/storage
- fileaccess_class_name: Name of the class implementing the file access
- default_schema=true: lets HSQLDB behave as if it doesn't support schemas
Desired Features
- single-file
This would allow to get rid of the temporary files which are currently needed when working on the embedded HSQLDB, and thus remove some performance penalties - separation of the "auto increment" from the "primary key" concept. Currently, if you declare a column to be an auto increment column, it inevidentely becomes the primary key
