Available on crate feature
postgres_backend
only.Expand description
Provides types and functions related to working with PostgreSQL
Much of this module is re-exported from database agnostic locations. However, if you are writing code specifically to extend Diesel on PostgreSQL, you may need to work with this module directly.
Modules
- Data structures for PG types which have no corresponding Rust type
- PostgreSQL related query builder extensions
- PostgreSQL specific SQL types
Structs
- Represents
DISTINCT ON (...)
- FailedToLookupTypeError
i-implement-a-third-party-backend-and-opt-into-breaking-changes
This error indicates that a type lookup for a custom postgres type failed - The PostgreSQL backend
- PgConnection
postgres
The connection string expected byPgConnection::establish
should be a PostgreSQL connection string, as documented at https://www.postgresql.org/docs/9.4/static/libpq-connect.html#LIBPQ-CONNSTRING - PgMetadataCache
i-implement-a-third-party-backend-and-opt-into-breaking-changes
Cache for the OIDs of custom Postgres types - PgMetadataCacheKey
i-implement-a-third-party-backend-and-opt-into-breaking-changes
The key used to lookup cached type oid’s inside of a PgMetadataCache. - The PostgreSQL query builder
- PgRowByRowLoadingMode
postgres
APgConnection
specific loading mode to load rows one by one - The OIDs for a SQL type
- Raw postgres value as received from the database
- Used to build a transaction, specifying additional details.
Traits
- GetPgMetadataCache
i-implement-a-third-party-backend-and-opt-into-breaking-changes
Gets thePgMetadataCache
for aConnection<Backend=Pg>
so that the lookup of user defined types, or types which come from an extension can be cached. - Determines the OID of types at runtime
- TypeOidLookup
i-implement-a-third-party-backend-and-opt-into-breaking-changes
This is a helper trait to defer a type oid lookup to a later point in time