Package com.codename1.backend.sql

package com.codename1.backend.sql

The database engines a backend talks to, and what they spell differently.

Postgres and MySql speak their engines' wire protocols directly, so a server binary needs no JDBC driver. Dialect renders one portable statement form for whichever engine a connection reaches. Most applications use them through com.codename1.backend.Database and never name these classes.

Server code: this package is not available in the app.

Related Packages

Package	Description
com.codename1.backend	The Codename One backend runtime: the server side of an application, written in the same Java as the app and compiled to a native server binary.
com.codename1.backend.annotations	Annotations that turn an ordinary class into an HTTP or websocket endpoint.
com.codename1.backend.aws	Amazon Web Services from a backend: request signing, credentials, and S3.
com.codename1.backend.orm	The build-time ORM on the server: entity classes in, typed data access objects out.
com.codename1.backend.otel	OpenTelemetry tracing for a backend, exported over OTLP/HTTP without an OpenTelemetry library.

Classes

Class	Description
Dialect	What the three engines spell differently, in one place.
MySql	A MySQL client speaking the client/server protocol directly, for the same reason as Postgres: a translated server binary has no JDBC.
Postgres	A PostgreSQL client speaking the v3 frontend/backend protocol directly.