Home >> All >> org >> apache >> derby >> impl >> tools

•	org.apache.derby.impl.tools.dblook.* (10)	•	org.apache.derby.impl.tools.ij.* (40)
•	org.apache.derby.impl.tools.sysinfo.* (2)

Package Samples:

• org.apache.derby.impl.tools.dblook
• org.apache.derby.impl.tools.ij
• org.apache.derby.impl.tools.sysinfo

Classes:

• ij: This parser works on a statement-at-a-time basis. It maintains a connection environment that is set by the caller and contains a list of connections for the current thread/ij session. Multi-user frameworks that use this parser tend to maintain multiple connectionEnv's and pass in the current one to set ij up. A connectionEnv has a default connection in use, and the ij connect/set connection/disconnect commands are used to change the current connection. Each connection has associated with it a list of prepared statements and cursors, created by the ij prepare and get cursor statements and manipulated ...
• Main: Copyright © 1998, Cloudscape, Inc. All rights reserved. SysInfo reports values relevant to the Cloudscape product found on the CLASSPATH. It looks for a file called sysinfo.properties in the CLASSPATH using getResourceAsStream. If the file is not found, or some other exception occurs, the value returned will be that set for the key SysInfo.failureTag, or be the value " ". This class can be used to print out system information at the command line by issuing the command: java org.apache.derby.tools.sysinfo Alternatively, you can use SysInfo within your program to display Cloudscape information; ...
• StatementFinder: StatementGrabber looks through an input stream for the next JSQL statement. A statement is considered to be any tokens up to the next semicolon or EOF. Semicolons inside comments, strings, and delimited identifiers are not considered to be statement terminators but to be part of those tokens. The only comment form currently recognized is the SQL comment, which begins with "--" and ends at the next EOL. Strings and delimited identifiers are permitted to contain newlines; the actual IJ or JSQL parsers will report errors when those cases occur. There are no escaped characters, i.e. "\n" is considered ...
• CharStream: This interface describes a character stream that maintains line and column number positions of the characters. It also has the capability to backup the stream to some extent. An implementation of this interface is used in the TokenManager implementation generated by JavaCCParser. All the methods except backup can be implemented in any fashion. backup needs to be implemented correctly for the correct operation of the lexer. Rest of the methods are all used to get information like line number, column number and the String that constitutes a token and are not used by the lexer. Hence their implementation ...
• Main: This is the controller for ij. It uses two parsers: one to grab the next statement, and another to see if it is an ij command, and if so execute it. If it is not an ij command, it is treated as a JSQL statement and executed against the current connection. ijParser controls the current connection, and so contains all of the state information for executing JSQL statements. This was written to facilitate a test harness for language functionality tests.
• Session: Session holds the objects local to a particular database session, which starts with a connection and is all other JDBC stuff used on that connection, along with some ij state that is connection-based as well. This is separated out to localize database objects and also group objects by session.
• ijException: ijException is used to get messages from the ij parser to the main ij loop. Because this is not under the protocol/impl umbrella, it does not have available to it the message service. At this time, all messages are hard-coded in this file. A more serviceable solution may need to be found.
• ParseException: This exception is thrown when parse errors are encountered. You can explicitly create objects of this exception type by calling the method generateParseException in the generated parser. You can modify this class to customize your error reporting mechanisms so long as you retain the public fields.
• ijWarningResult: This is an impl for just returning warnings from JDBC objects we don't want the caller to touch. They are already cleared from the underlying objects, doing clearSQLWarnings here is redundant.
• ijRowResult: This is an impl for when 1 row of a result set is the intended use of it. The caller *must not* do a "next" on the result set. It's up to them to make sure that doesn't happen.
• Main14: This is the controller for the JDBC3.0 version of ij. This was written to facilitate a test harness for the holding cursors over commit functionality in JDBC3.0.
• utilMain: This class is utilities specific to the two ij Main's. This factoring enables sharing the functionality for single and dual connection ij runs.
• utilMain14: This class is utilities specific to the two ij Main's. This factoring enables sharing the functionality for single and dual connection ij runs.
• SimpleCharStream: An implementation of interface CharStream, where the stream is assumed to contain only ASCII characters (without unicode processing).
• ijMultiResult: This is an impl for a statement execution; the result is either an update count or result set depending on what was executed.
• ijStatementResult: This is an impl for a statement execution; the result is either an update count or result set depending on what was executed.
• ijExceptionResult: This is an impl for just returning errors from JDBC statements. Used by Async to capture its result for WaitFor.
• UCode_CharStream: An implementation of interface CharStream, where the stream is assumed to contain only Unicode characters.
• mtTester: mtTester grabs test and runs them forever. The spawner of tester is responsible for killing it.
• util: Methods used to control setup for apps as well as display some internal ij structures.
• ijResult: This is a wrapper for results coming out of the ij parser.
• ijVectorResult: This is an impl for a simple Vector of strings.
• ijResultImpl: This is an empty impl for reuse of code.
• ConnectionEnv: To enable multi-user use of ij.Main2
• Token: Describes the input token stream.

Home | Contact Us | Privacy Policy | Terms of Service