Java DB

Apache Derby

Derby Tools and Utilities Guide

Derby Getting Started
Derby Reference Manual
Derby Developer's Guide
Derby Performance Tuning
Derby Server and Admin Guide
Derby Tools and Utilities
Derby Tools and Utilities
-Copyright
-License
-About this guide
-What are the Derby tools and utilities?
-Using ij
-ij properties reference
-ij commands and errors reference
-ij commands
-Absolute command
-After Last command
-Async command
-Autocommit command
-Before First command
-Close command
-Commit command
-Connect command
-Describe command
-Disconnect command
-Driver command
-Elapsedtime command
-Execute command
-Exit command
-First command
-Get Cursor command
-Get Scroll Insensitive Cursor command
-Help command
-Last command
-LocalizedDisplay command
-MaximumDisplayWidth command
-Next command
-Prepare command
-Previous command
-Protocol command
-Readonly command
-Relative command
-Remove command
-Rollback command
-Run command
-Set Connection command
-Show command
-Wait For command
-Syntax for comments in ij commands
-Syntax for identifiers in ij commands
-Syntax for strings in ij commands
-ij errors
-Using the bulk import and export procedures
-Storing jar files in a database
-sysinfo
-dblook
-SignatureChecker
-Trademarks

 

Protocol command

Syntax

PROTOCOL String [ AS Identifier ]

Description

Specifies the protocol, as a String, for establishing connections and automatically loads the appropriate driver. Protocol is the part of the database connection URL syntax appropriate for your environment, including the JDBC protocol and the protocol specific to Derby. For further information about the Derby database connection URL, see the Derby Developer's Guide. Only Derby protocols are supported. Those protocols are listed in ij.protocol property.

Providing a protocol allows you to use a shortened database connection URL for connections. You can provide only the database name (and a subsubprotocol name if needed) instead of the full protocol. In addition, you do not need to use the Driver command or specify a driver at start-up, since the driver is loaded automatically.

If you name the protocol, you can refer to the protocol name in the Connect command.

Examples

ij> protocol 'jdbc:derby:';
ij> connect 'sample';
ij> protocol 'jdbc:derby:';
ij> connect 'memory:sample;create=true';
ij> protocol 'jdbc:derby:memory:';
ij> connect 'sample;create=true';
 

javadb@jdbcurl.com