HSQLDB

To stop the HSQLDB server, all that's needed is a SHUTDOWN command as an SQL statement.

A project named . hsqldb is created, if it does not exist, and inside it the engine will look for database. script and other database files.

During shutdown, the HSQLDB engine will generate a new database. script file with the minimum set of statements for fast database startup.

We'll use the new nature simply as a way to make HSQLDB actions available (or not available) for specific projects.

The first step in building our set of plug-ins is to package HSQLDB itself as an Eclipse plug-in.

We need to replace the HSQLDB workbench preferences page by an HSQLDB resource property page.

Provide help docs for the plug-in itself, and include HSQLDB docs in a format suitable for the Workbench help manager.

The state of the HSQLDB database is shown in Figure 1.

Grails comes pre-packaged with HSQLDB, but since we're using MySQL, we have a few quick steps to tell Grails how to talk to our database.

Copy hsqldb. jar from your HSQLDB installation to the project directory and add it to the Runtime of the project.

And which can add builders and other elements to the workbench, but for this second release HSQLDB plugin does not need to do anything.

Of course, HSQLDB connection parameters should be stored on a per-project basis, instead of only once for the whole workbench.

That's the reason the second version of the HSQLDB plugin defines a new classpath variable to hold a reference to hsqldb. jar.

The code was tested using an in-memory database called HSQLDB, and this product includes a simple GUI tool.

This class will contain all code that deals directly with HSQLDB, keeping the contributed extensions code simple.

You can download HSQLDB, including sources and documentation, from SourceForge (hsqldb. sourceforge. net; see the link in Resources).

HSQLDB was really created for embedded applications, not for the corporate data center.

HSQLDB is Licensed under a liberal BSD style license. EffiProz is free for none commercial use (Academic, Research, etc. ).

Two possibilities immediately sprang to mind; HSQLDB, the open-source in-memory SQL database, and XQuery.

You can download HSQLDB from this site and use it as the database for the sample application.

This process is used as the key for a Map whose stored values are Java Project (HSQLDB Engine) references.

Besides the default memory tables, HSQLDB also supports "cached" and "text" tables.

Client developers, who simply use HSQLDB as a repository for data.

Besides having extra actions, a DB Engine Project needs access to the HSQLDB server classes.

Engine developers, who want to extend the SQL dialect recognized by HSQLDB by adding either new scalar functions or stored procedures.

The "HSQLDB" submenu, visible for any Java Project, containing two groups of items.

If we provide a way to add the HSQLDB Engine project nature to a Java Project, it's natural we provide a way to remove this nature.

The key to HSQLDB's simplicity is the serialization of SQL statement execution.

Thanks HSQLDB group and please read their license before you continue .

data, which contains configuration files used by HSQLDB.

The method stopHsqldb from hsqldb. ui. HsqldbUtil, shown in Listing 5, does just that.

Name its main class (Plugin class) PluginUi, accepting the default package name hsqldb. ui.

In development and test mode, HSQLDB uses an in-memory datastore.

But, when there's no server running, we can run the Database Manager in stand-alone mode, where the HSQLDB engine runs in-process.

I've started the HSQLDB database in embedded mode using the memory-based database option.

You now have Grails using a database other than HSQLDB.

Now that we can have HSQLDB Projects in the workspace, their custom actions need implementation classes.

The code needs only the Hibernate and HSQLDB libraries in order to compile and run properly.

Every Java project will get an HSQLDB menu.

Developers of the first kind need easy access to the HSQLDB JDBC driver so they can submit SQL statements.

There's no explicit way to create HSQLDB databases.

Run SQL script files using the HSQLDB ScriptTool utility.

HSQLDB supports a rich subset of ANSI-92 SQL and also SQL 99 and 2003 enhancements.

HSQLDB is an open source, lightweight, pure-Java SQL database engine, licensed under a BSD-style license.

HSQLDB keeps all table and index data in memory, saving all SQL statements issued into a file named

The HSQLDB engine can be run in many modes to suit different application scenarios

If you prefer to edit XML code directly, Listing 2 shows the complete plugin. xml file for the hsqldb. ui

Termination of HSQLDB server instances

Listing 5. plugin. xml manifest file snippet for the HSQLDB project property page

Listing 3. plugin. xml manifest file snippet defining the HSQLDB Engine Project Nature

Listing 4. plugin. xml manifest file snippet defining the HSQLDB menu actions

How to write a plug-in that integrates the HSQLDB database server into the Eclipse Workbench

It is easy to identify two kinds of developers interested in HSQLDB integration into the Eclipse workbench