You may set it to 0 to disable the timeout, or the specific timeout you'd like, in milliseconds. The default timeout is 60 seconds for any JDBC command. timeout - In DbVisualizer, set the Timeout in the Properties tab on the connection configuration.Setting the “rootIsCatalog” flag true will cause the driver to skip enumerating the top level schemas, and only expose root as a catalog. This can be problematic if the user connecting doesn’t have permissions to the root container (ie, is not an admin) attempting to enumerate the top level schemas results in a 403 (Forbidden) response. Ordinarily we might expose the schemas for the LabKey Server root container at both the top level of a tree, and in a catalog with name "/". Note that folders and projects in LabKey Server are exposed as individual catalogs (databases) through the jdbc driver. Otherwise the schemas/tables will also be exposed at the top level of the tree. rootIsCatalog - Setting rootIsCatalog true will force the root container on the server to only be exposed as a catalog in calls to getTables().The driver supports the following properties, which can be set either in Java code by setting in the Properties handed to to DriverManager.getConnection(), or by setting on the Connection that is returned by calling setClientInfo(). Password: Associated with an account on the web server.Username: Associated with an account on the web server.You may include a folder path after a # to set the default target, without the need to explicitly set a catalog through JDBC. Examples include "jdbc:labkey: and "jdbc:labkey: ". Database URL: The base URL of the web server, including any context path, prefixed with "jdbc:labkey:".Note this this driver jar also contains the LabKey Java client api and all of its dependencies. Click labkey-api-jdbc-X.X.X.jar (X.X.X will be the release number/name).See the driver listed under Current Binaries. The 1.x version supports Java 8 contact your account manager if you need a copy of the older JDBC driver. Note that the 2.x version of the JDBC driver requires Java 17. The JDBC driver is included in the Professional and Enterprise distributions of LabKey Server. Other tools may work with the driver as it is currently implemented, but some tools may require driver functionality that has not yet been implemented. The following client applications have been successfully tested with the driver: Schemas within a given container are exposed as JDBC schemas. Update, insert, and delete operations are not supported.Ĭontainers (projects and folders) are exposed as JDBC catalogs. It implements a subset of the full JDBC functionality, supporting read only (SELECT) access to the data. The JDBC driver for LabKey Server allows client applications to query against the schemas, tables, and queries that LabKey Server exposes using LabKey SQL. Premium Feature - Available in the Professional and Enterprise Editions of LabKey Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |