|Home >> All >> org >> [ hsql Javadoc ]|
|||org.hsqldb.lib.* (6)||||org.hsqldb.sample.* (4)||||org.hsqldb.test.* (11)||||org.hsqldb.util.* (42)|
org.hsql: Javadoc index of package org.hsql.
jdbcResultSet: Implements both the java.sql.ResultSet and java.sql.ResultSetMetaData interfaces. In short: A ResultSet object is essentially--but not limited to being--a table of data representing a database result set, which is usually generated by executing a statement that queries the database. A ResultSetMetaData object is one that can be used to get information about the types and properties of the columns in a ResultSet object. The following is composed of three sections: The generic overview for ResultSet . The generic overview for ResultSetMetaData . A discussion of some HSQLDB-specific concerns. From ...
jdbcPreparedStatement: Implements both the java.sql.PreparedStatement and java.sql.CallableStatement interfaces. In short: A PreparedStatement is used to precompile and execute SQL statements, possibly using parameters. A CallableStatement is used to execute SQL stored procedures. The following is composed of three sections: The generic overview for PreparedStatement . The generic overview for CallableStatement . A discussion of some HSQLDB-specific concerns. From PreparedStatement : An object that represents a precompiled SQL statement. A SQL statement is precompiled and stored in a PreparedStatement object. This object ...
jdbcConnection: A connection (session) with a specific database. Within the context of a Connection, SQL statements are executed and results are returned. A Connection's database is able to provide information describing its tables, its supported SQL grammar, its stored procedures, the capabilities of this connection, and so on. This information is obtained with the getMetaData method. Note: By default the Connection automatically commits changes after executing each statement. If auto commit has been disabled, an explicit commit must be done or database changes will not be saved. HSQLDB-Specific Information: ...
jdbcDatabaseMetaData: Comprehensive information about the database as a whole. This interface is implemented by driver vendors to let users know the capabilities of a Database Management System (DBMS) in combination with the driver based on JDBC TM technology ("JDBC driver") that is used with it. Different relational DBMSs often support different features, implement features in different ways, and use different data types. In addition, a driver may implement a feature on top of what the DBMS offers. Information returned by methods in this interface applies to the capabilities of a particular driver and a particular ...
jdbcStatement: The object used for executing a static SQL statement and returning the results it produces. By default, only one ResultSet object per Statement object can be open at the same time. Therefore, if the reading of one ResultSet object is interleaved with the reading of another, each must have been generated by different Statement objects. All execution methods in the Statement interface implicitly close a statment's current ResultSet object if an open one exists. HSQLDB-Specific Information: JRE 1.1.x Notes: In general, JDBC 2 support requires Java 1.2 and above, and JDBC3 requires Java 1.4 and above. ...
TriggerSample: Sample code for use of triggers in hsqldb. SQL to invoke is: CREATE TRIGGER triggerSample BEFORE|AFTER INSERT|UPDATE|DELETE ON myTable [FOR EACH ROW] [QUEUE n] [NOWAIT] CALL "myPackage.trigClass" This will create a thread that will wait for its firing event to occur; when this happens, the trigger's thread runs the 'trigClass.fire' Note that this is still in the same Java Virtual Machine as the database, so make sure the fired method does not hang. There is a queue of events waiting to be run by each trigger thread. This is particularly useful for 'FOR EACH ROW' triggers, when a large number of ...
jdbcDriver: Each JDBC driver must supply a class that implements the Driver interface. The Java SQL framework allows for multiple database drivers. The DriverManager will try to load as many drivers as it can find and then for any given connection request, it will ask each driver in turn to try to connect to the target URL. The application developer will normally not need to call any function of the Driver directly. All required calls are made by the DriverManager. When the HSQL Database Engine Driver class is loaded, it creates an instance of itself and register it with the DriverManager. This means that ...
Server: Server acts as a database server and is one way of using the client-server mode of HSQL Database Engine. This server can only process database queries. An applet or application will use only the JDBC classes to access the database. The Server can be configured with the file 'server.properties'. This is an example of the file: server.port=9001 server.database=test server.silent=true If the server is embedded in an application server, such as when DataSource or HsqlServerFactory classes are used, it is necessary to avoid calling System.exit() when the HSQLDB is shutdown with an SQL command. For this, ...
Log: This class is responsible for most file handling. A HSQL database consists of a .properties file, a .script file (contains a SQL script), a .data file (contains data of cached tables) and a .backup file (contains the compressed .data file) This is an example of the .properties file. The version and the modified properties are automatically created by the database and should not be changed manually: modified=no version=1.43 The following lines are optional, this means they are not created automatically by the database, but they are interpreted if they exist in the .script file. They have to be created ...
CodeSwitcher: Modifies the source code to support different JDK or profile settings. Usage: java CodeSwitcher [paths] [labels] [+][-] If no labels are specified then all used labels in the source code are shown. Use +MODE to switch on the things labeld MODE Use -MODE to switch off the things labeld MODE Path: Any number of path or files may be specified. Use . for the current directory (including sub-directories). Example: java CodeSwitcher +JAVA2 . This example switches on code labeled JAVA2 in all *.java files in the current directory and all subdirectories. java CodeSwitcher + . Adds test code to the code. ...
Servlet: Servlet acts as a interface between the applet and the database for the the client / server mode of HSQL Database Engine. It is not required if the included HSQL Database Engine WebServer is used, but if another HTTP server is used. The HTTP Server must support the Servlet API. This class should not be used directly by the application. It will be called by the HTTP Server. The applet / application should use the jdbc* classes. The database name is taken from the servlet engine (extranal webserver) property hsqldb.server.database (fredt@users)
TestCacheSize: Test large cached tables by setting up a cached table of 100000 records or more and a much smaller memory table with about 1/100th rows used. Populate both tables so that an indexed column of the cached table has a foreign key reference to the main table. This database can be used to demonstrate efficient queries to retrieve the data from the cached table. insert timings for 100000 rows, cache scale 12: simple table, no extra index: 52 s with index on lastname only: 56 s with index on zip only: 211 s foreign key, referential_integrity true: 216 s
HsqlName: Name of an SQL object Methods check user defined names and issue system generated names for SQL objects. This class does not deal with the type of the SQL object for which it is used. sysNumber is used to generate system generated names. It is set to the largest integer encountered in names that use the SYS_xxxxxxx_INTEGER format. As the DDL is processed before any ALTER command, any new system generated name will have a larger integer suffix than all the existing names.
HypersonicDBServlet: Database Servlet handling the access to the HyperSonic SQL database. Unfortunately, in the current version 1.6.0 of org.hsqldb.Serlvet, the database filename is not configurable, but it has to be set fixed in the constructor. This does not fit to the servlet API. Hence, we import the sourcecode of org.hsqldb.Serlvet in the hope, that this will be fixed in the future. Created: Sun Nov 12 07:41:51 2000
DatabaseManagerSwing: Swing Tool for manageing a JDBC database. Usage: java DatabaseManagerSwing [-options] where options include: -driver jdbc driver class -url jdbc url -user username used for connection -password password for this user -dir default directory -script reads from script file
DatabaseManager: AWT Tool for manageing a JDBC database. Usage: java DatabaseManagerSwing [-options] where options include: -driver jdbc driver class -url jdbc url -user username used for connection -password password for this user -dir default directory -script reads from script file
DiskNode: Cached table Node implementation. Only integral references to left, right and parent nodes in the AVL tree are held and used as offsets to disk data. tTable is a reference to the table for this node and is used to get a linked node in the tree. iId is a reference to the Index object that contains this node. These fields can be eliminated in the future, by changing the method signatures to take a Table parameter from Index.java (fredt@users)
ServerConnection: All ServerConnection objects are listed in a Vector in mServer and removed when closed. When a connection is dropped or closed the Server.notify() method is called. Upon notification, tf the DB is shutdown as a result of SHUTDOWN, the server stops all ServerConnection threads. At this point, only the skeletal Server object remains and everything else will be garbage collected. (fredt@users)
Node: The parent for all AVL node implementations, features factory methods for its subclasses. Subclasses of Node vary in the way they hold references to other nodes in the AVL tree. nNext links the Node objects belonging to different indexes for each table row. It is used solely by Row to locate the node belonging to a particular index. (fredt@users)
Database: Database is the root class for HSQL Database Engine database. Although it either directly or indirectly provides all or most of the services required for DBMS functionality, this class should not be used directly by an application. Instead, to achieve portability and generality, the jdbc* classes should be used.
PointerNode: Text table node implementation. Nodes for the AVL tree are all built and kept in memory while the actual row data is accessed through TextCache from disk. This extends MemoryNode by maintaining a disk based offset for the Row data. (fredt@users)
HsqlDateTime: collection of static methods to convert Date, Time and Timestamp strings into corresponding Java objects. Also accepts SQL literals such as NOW, TODAY as valid strings and returns the current date / time / datetime. Compatible with jdk 1.1.x
HsqlDeque: jdk 1.1 compatible minimal implementation of a list object suitable for stack, queue and deque usage patterns backed by an Object. The memory footprint of the HsqlDeque doubles when it gets full but does not shrink when it gets empty.
UserManager: The collection (Vector) of User object instances within a specific database. Methods are provided for creating, modifying and deleting users, as well as manipulating their access rights to the database objects.