Difference between revisions of "HSQLDB Integration"

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

Revision as of 07:39, 4 May 2006

This is a (more technically orientated) page about the integration of the HSQLDB engine[1] into OpenOffice.org.

Connection settings which are currently necessary to connect to HSQLDB embedded in an OpenOffice.org database file

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 inevitable becomes the primary key
editable views
Currently, if you create a view as simple as SELECT * FROM table, this is not updateable, even if table itself is.
(side note: Hmm, have to check which part OOo plays here - perhaps it's OOo's fault in real?)

@@ Line 15: / Line 15: @@
 [[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 inevitable becomes the primary key
-* editable views<br/>Currently, if you create a view as simple as <code>SELECT * FROM table</code<, this is not updateable, even if <code>table</code> itself is.<br/>
+* editable views<br/>Currently, if you create a view as simple as <code>SELECT * FROM table</code>, this is not updateable, even if <code>table</code> itself is.<br/>(side note: Hmm, have to check which part OOo plays here - perhaps it's OOo's fault in real?)
-(side note: Hmm, have to check which part OOo plays here - perhaps it's OOo's fault in real?)