| Home >> All >> com >> mysql |
| • | com.mysql.jdbc.* (52) | • | com.mysql.jdbc.jdbc2.* (8) | • | com.mysql.jdbc.jdbc2.optional.* (8) |
| • | com.mysql.jdbc.util.* (2) |
Package Samples:
• com.mysql.jdbc.jdbc2.optional
• com.mysql.jdbc.util
• com.mysql.jdbc
Classes:
• ResultSet: A ResultSet provides access to a table of data generated by executing a Statement. The table rows are retrieved in sequence. Within a row its column values can be accessed in any order. A ResultSet maintains a cursor pointing to its current row of data. Initially the cursor is positioned before the first row. The 'next' method moves the cursor to the next row. The getXXX methods retrieve column values for the current row. You can retrieve values either using the index number of the column, or by using the name of the column. In general using the column index will be more efficient. Columns are ...
• BaseBugReport: Base class to help file bug reports for Connector/J. MySQL AB really appreciates repeatable testcases when reporting bugs, so we're giving you this class to make that job a bit easier (and standarized). To create a testcase, create a class that inherits from this class (com.mysql.jdbc.util.BaseBugReport), and override the methods 'setUp', 'tearDown' and 'runTest'. In the 'setUp' method, create code that creates your tables, and populates them with any data needed to demonstrate the bug. In the 'runTest' method, create code that demonstrates the bug using the tables and data you created in the 'setUp' ...
• Blob: The representation (mapping) in the JavaTM programming language of an SQL BLOB value. An SQL BLOB is a built-in type that stores a Binary Large Object as a column value in a row of a database table. The driver implements Blob using an SQL locator(BLOB), which means that a Blob object contains a logical pointer to the SQL BLOB data rather than the data itself. A Blob object is valid for the duration of the transaction in which is was created. Methods in the interfaces ResultSet, CallableStatement, and PreparedStatement, such as getBlob and setBlob allow a programmer to access an SQL BLOB value. ...
• NonRegisteringDriver: The Java SQL framework allows for multiple database drivers. Each driver should supply a class that implements the Driver interface 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. It is strongly recommended that each Driver class should be small and standalone so that the Driver class can be loaded and queried without bringing in vast quantities of supporting code. When a Driver class is loaded, it should create an instance of itself and register it with the DriverManager. ...
• Driver: The Java SQL framework allows for multiple database drivers. Each driver should supply a class that implements the Driver interface 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. It is strongly recommended that each Driver class should be small and standalone so that the Driver class can be loaded and queried without bringing in vast quantities of supporting code. When a Driver class is loaded, it should create an instance of itself and register it with the DriverManager. ...
• DatabaseMetaData: JDBC Interface to Mysql functions This class provides information about the database as a whole. Many of the methods here return lists of information in ResultSets. You can use the normal ResultSet methods such as getString and getInt to retrieve the data from these ResultSets. If a given form of metadata is not available, these methods show throw a java.sql.SQLException. Some of these methods take arguments that are String patterns. These methods all have names such as fooPattern. Within a pattern String "%" means match any substring of 0 or more characters and "_" means match any one character ...
• ConnectionWrapper: This class serves as a wrapper for the org.gjt.mm.mysql.jdbc2.Connection class. It is returned to the application server which may wrap it again and then return it to the application client in response to dataSource.getConnection(). All method invocations are forwarded to org.gjt.mm.mysql.jdbc2.Connection unless the close method was previously called, in which case a sqlException is thrown. The close method performs a 'logical close' on the connection. All sqlExceptions thrown by the physical connection are intercepted and sent to connectionEvent listeners before being thrown to client.
• PreparedStatement: A SQL Statement is pre-compiled and stored in a PreparedStatement object. This object can then be used to efficiently execute this statement multiple times. Note: The setXXX methods for setting IN parameter values must specify types that are compatible with the defined SQL type of the input parameter. For instance, if the IN parameter has SQL type Integer, then setInt should be used. If arbitrary parameter type conversions are required, then the setObject method should be used with a target SQL type.
• Statement: A Statement object is used for executing a static SQL statement and obtaining the results produced by it. Only one ResultSet per Statement can be open at any point in time. Therefore, if the reading of one ResultSet is interleaved with the reading of another, each must have been generated by different Statements. All statement execute methods implicitly close a statement's current ResultSet if an open one exists.
• Connection: A Connection represents a 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, etc. This information is obtained with the getMetaData method.
• CharsetMapping: Mapping between MySQL charset names and Java charset names. I've investigated placing these in a .properties file, but unfortunately under most appservers this complicates configuration because the security policy needs to be changed by the user to allow the driver to read them :(
• MysqlConnectionPoolDataSource: This class is used to obtain a physical connection and instantiate and return a MysqlPooledConnection. J2EE application servers map client calls to dataSource.getConnection to this class based upon mapping set within deployment descriptor. This class extends MysqlDataSource.
• OutputStreamWatcher: Objects that want to be notified of lifecycle events on a WatchableOutputStream should implement this interface, and register themselves with setWatcher() on the WatchableOutputStream instance.
• WriterWatcher: Objects that want to be notified of lifecycle events on a WatchableWriter should implement this interface, and register themselves with setWatcher() on the WatchableWriter instance.
• SingleByteCharsetConverter: Converter for char[]->byte[] and byte[]->char[] for single-byte character sets. Much faster (5-6x) than the built-in solution that ships with the JVM, even with JDK-1.4.x and NewIo.
• MysqlPooledConnection: This class is used to wrap and return a physical connection within a logical handle. It also registers and notifies ConnectionEventListeners of any ConnectionEvents
• RowData: This interface abstracts away how row data is accessed by the result set. It is meant to allow a static implementation (Current version), and a streaming one.
• Debug: The Debug class allows debug messages on a per-class basis. The user issues a trace() call, listing the classes they wish to debug.
• TimezoneDump: Dumps the timezone of the MySQL server represented by the JDBC url given on the commandline (or localhost/test if none provided).
• LicenseConfiguration: Used in commercially-licensed clients that require connections to commercially-licensed servers as part of the licensing terms.
• ResultSetMetaData: A ResultSetMetaData object can be used to find out about the types and properties of the columns in a ResultSet
• SQLError: SQLError is a utility class that maps MySQL error codes to X/Open error codes as is required by the JDBC spec.
• PreparedStatementWrapper: Wraps prepared statements so that errors can be reported correctly to ConnectionEventListeners.
• CompressedInputStream: Used to de-compress packets from the MySQL server when protocol-level compression is turned on.
| Home | Contact Us | Privacy Policy | Terms of Service |