Client and backend. Every class listed here is shared: the same code is compiled into your app and into your server. The package's page in the client API lists all of it, including any classes that exist only in the app.

package com.codename1.db.sql

Database servers over their own wire protocols, with no JDBC driver: Postgres, MySql, SqlServer and Oracle, each a ServerSession. Dialect renders one portable statement form for whichever engine a session reaches.

An application carries only the engines it names. On the client, construct one of the com.codename1.db.ServerDatabase subclasses; on the server, the backend’s Database opens the engines its declared URLs name.

Types

class DialectWhat the three engines spell differently, in one place.
class EnginesThe server engines a database URL can name: their schemes, canonical names and default ports.
class MySqlA MySQL client speaking the client/server protocol directly, for the same reason as Postgres: a translated server binary has no JDBC.
class OracleAn Oracle Database client speaking TNS and TTC, the protocol of Oracle’s own “thin” drivers.
class PostgresA PostgreSQL client speaking the v3 frontend/backend protocol directly.
class ServerSessionAn open session with a database server: Postgres, MySql, SqlServer or Oracle.
class SqlFailureA database error that a caller can act on: a transaction that lost a race with another one (CONCURRENCY) or a write a constraint refused (INTEGRITY).
class SqlPlatformWhat the wire clients need from the target they run on: a socket, random bytes, and the exceptions a caller catches.
class SqlServerA SQL Server client speaking TDS 7.4, the Tabular Data Stream, written from Microsoft’s published MS-TDS specification.
class SqlSocketA connection to a database server, as the wire clients in this package see it.
enum TransactionIsolationThe transaction isolation a caller asks a wire client for.