Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.postgresql.fastpath.* (2)org.postgresql.geometric.* (7)org.postgresql.jdbc1.* (7)
org.postgresql.jdbc2.* (7)org.postgresql.largeobject.* (3)org.postgresql.util.* (6)
org.postgresql.xa.* (6)

org.postgresql: Javadoc index of package org.postgresql.


Package Samples:

org.postgresql.fastpath
org.postgresql.geometric
org.postgresql.jdbc1
org.postgresql.jdbc2
org.postgresql.largeobject
org.postgresql.util
org.postgresql.xa

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 ...
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 ...
TwoPhaseConnection: Defines two-phase commit support for a JDBC connection used by XAConnection . A JDBC connection that can implement any of these features should extend this interface and attempt to implement as much as it can. prepare() 55 is used as part of the two phase commit protocol to determine whether the transaction can commit or must rollback. Failure to implement this method will cause all connections to vote for commit, whether or not they can actually commit, leading to mixed heuristics. enableSQLTransactions(boolean) 55 allows the SQL begin/commit/rollback commands to be disabled for the duration of ...
CallableStatement: CallableStatement is used to execute SQL stored procedures. JDBC provides a stored procedure SQL escape that allows stored procedures to be called in a standard way for all RDBMS's. This escape syntax has one form that includes a result parameter and one that does not. If used, the result parameter must be registered as an OUT parameter. The other parameters may be used for input, output or both. Parameters are refered to sequentially, by number. The first parameter is 1. {?= call [ , , ...]} {call [ , , ...]} IN parameter values are set using the set methods inherited from PreparedStatement. The ...
CallableStatement: CallableStatement is used to execute SQL stored procedures. JDBC provides a stored procedure SQL escape that allows stored procedures to be called in a standard way for all RDBMS's. This escape syntax has one form that includes a result parameter and one that does not. If used, the result parameter must be registered as an OUT parameter. The other parameters may be used for input, output or both. Parameters are refered to sequentially, by number. The first parameter is 1. {?= call [ , , ...]} {call [ , , ...]} IN parameter values are set using the set methods inherited from PreparedStatement. The ...
LargeObjectManager: This class implements the large object interface to org.postgresql. It provides methods that allow client code to create, open and delete large objects from the database. When opening an object, an instance of org.postgresql.largeobject.LargeObject is returned, and its methods then allow access to the object. This class can only be created by org.postgresql.Connection To get access to this class, use the following segment of code: import org.postgresql.largeobject.*; Connection conn; LargeObjectManager lobj; ... code that opens a connection ... lobj = ((org.postgresql.Connection)myconn).getLargeObjectAPI(); ...
XAConnectionImpl: Implements an X/A connection that can be pooled and managed from inside a transaction monitor. This is the XA connection returned to the application server from the XADataSourceImpl and will be used to obtain ClientConnection for the application. If the transaction is managed through the JDBC interface, this connection will reference the underlying JDBC connection directly. If this resource is enlisted with a global transaction through the javax.transaction.xa.XAResource interface, it will reference a transactional connection, or TxConnection . Such a connection may be shared by two or more XA ...
DatabaseMetaData: 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 should throw a SQLException. Some of these methods take arguments that are String patterns. These arguments 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. Only metadata entries matching the ...
DatabaseMetaData: 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 should throw a SQLException. Some of these methods take arguments that are String patterns. These arguments 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. Only metadata entries matching the ...
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. ...
LargeObject: This class implements the large object interface to org.postgresql. It provides the basic methods required to run the interface, plus a pair of methods that provide InputStream and OutputStream classes for this object. Normally, client code would use the getAsciiStream, getBinaryStream, or getUnicodeStream methods in ResultSet, or setAsciiStream, setBinaryStream, or setUnicodeStream methods in PreparedStatement to access Large Objects. However, sometimes lower level access to Large Objects are required, that are not supported by the JDBC specification. Refer to org.postgresql.largeobject.LargeObjectManager ...
Connection: $Id: Connection.java,v 1.1.1.1 2002/01/22 08:52:20 synmscott Exp $ 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. Note: By default, the Connection automatically commits changes after executing each statement. If auto-commit has been disabled, an explicit commit must be ...
Connection: $Id: Connection.java,v 1.1.1.1 2002/01/22 08:52:03 synmscott Exp $ 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. Note: By default, the Connection automatically commits changes after executing each statement. If auto-commit has been disabled, an explicit commit must be ...
Fastpath: This class implements the Fastpath api. This is a means of executing functions imbeded in the org.postgresql backend from within a java application. It is based around the file src/interfaces/libpq/fe-exec.c Implementation notes: Network protocol: The code within the backend reads integers in reverse. There is work in progress to convert all of the protocol to network order but it may not be there for v6.3 When fastpath switches, simply replace SendIntegerReverse() with SendInteger()
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.
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.
ClientConnection: Encapsulates an application's view of an XA/pooled connection. The XA connection is managed by the application server through it's javax.sql.XAConnection interface. The underlying JDBC connection is a standard JDBC connection. The application's JDBC connection gives access to the underlying JDBC connection but is managed by the application server. The application is given an instance of this class and not the underlying connection directly.
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.
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.
Serialize: This class uses PostgreSQL's object oriented features to store Java Objects. It does this by mapping a Java Class name to a table in the database. Each entry in this new table then represents a Serialized instance of this class. As each entry has an OID (Object IDentifier), this OID can be included in another table. This is too complex to show here, and will be documented in the main documents in more detail.
XADataSourceImpl: Implements a JDBC 2.0 javax.sql.XADataSource for any JDBC driver with JNDI persistance support. The base implementation is actually provided by a different javax.sql.DataSource class; although this is the super class, it only provides the pooling and XA specific implementation.
TxConnection: Describes an open connection associated with a transaction. When a transaction is opened for a connection, this record is created for the connection. It indicates the underlying JDBC connection and transaction Xid. Multiple XA connection that fall under the same transaction Xid will share the same TxConnection object.
UnixCrypt: This class provides us with the ability to encrypt passwords when sent over the network stream Contains static methods to encrypt and compare passwords with Unix encrypted passwords. See John Dumas's Java Crypt page for the original source.
PGobject: org.postgresql.PG_Object is a class used to describe unknown types An unknown type is any type that is unknown by JDBC Standards As of PostgreSQL 6.3, this allows user code to add their own handlers via a call to org.postgresql.Connection. These handlers must extend this class.
FastpathArg: Each fastpath call requires an array of arguments, the number and type dependent on the function being called. This class implements methods needed to provide this capability. For an example on how to use this, refer to the org.postgresql.largeobject package

Home | Contact Us | Privacy Policy | Terms of Service