JDBC Driver for HarperDB

Build 23.0.8839


To perform multiple inserts in a single request to HarperDB, use the INSERT INTO SELECT syntax to insert a temporary table of data into HarperDB. This works by first populating a temporary table with the data you are going to submit to HarperDB. Once you have all of the data you want to insert, the temporary table is then passed into the table in HarperDB.

This functionality is also available via the standard Batch Processing API available in JDBC. See Batch Processing for more information.

Populate the Temporary Table

The temporary table you are populating is dynamic and is created at run time the first time you insert to it. Temporary tables are denoted by a # appearing in their name. When using a temporary table to insert, the temporary table must be named in the format [TableName]#TEMP, where TableName is the name of the table you will be inserting to. For example:

INSERT INTO [HarperDB].[cstest].Cutomers#TEMP (CompanyName, MyCustomField__c) VALUES ('New Cutomers', '9000');
INSERT INTO [HarperDB].[cstest].Cutomers#TEMP (CompanyName, MyCustomField__c) VALUES ('New Cutomers 2', '9001');
INSERT INTO [HarperDB].[cstest].Cutomers#TEMP (CompanyName, MyCustomField__c) VALUES ('New Cutomers 3', '9002');

This creates a temporary table called [HarperDB].[cstest].Cutomers#TEMP with two columns and three rows of data. Since type cannot be determined on the temporary table itself, all values are stored in memory as strings. They are later converted to the proper type when they are submitted to the [HarperDB].[cstest].Cutomers table.

Insert to the Actual Table

Once your temporary table is populated, it is now time to insert to the actual table in HarperDB. You can do this by performing an INSERT to the actual table and selecting the input data from the temporary table. For example:

INSERT INTO [HarperDB].[cstest].Cutomers (CompanyName, MyCustomField__c) SELECT CompanyName, MyCustomField__c FROM [HarperDB].[cstest].Cutomers#TEMP
In this example, the full contents of the [HarperDB].[cstest].Cutomers#TEMP table are passed into the [HarperDB].[cstest].Cutomers table. This results in fewer requests being submitted to HarperDB since multiple INSERTs may be submitted with each request, which is much better for performance if you have many records to insert.


The results of the query are stored in the LastResultInfo#TEMP temporary table. This table is cleared and repopulated the next time data is modified by passing in a temporary table. Please be aware that the LastResultInfo#TEMP table has no predefined schema. You need to check its metadata at run time before reading data.

Temporary Table Life Span

Temporary tables only last as long as the connection remains open. When the connection to HarperDB is closed, all temporary tables are cleared, including the LastResultInfo#TEMP table.

Copyright (c) 2024 CData Software, Inc. - All rights reserved.
Build 23.0.8839