Struct Postgres 

pub struct Postgres;

Trait Implementations

impl Clone for Postgres

fn clone(&self) -> Postgres

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Copy for Postgres

impl Debug for Postgres

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for Postgres

fn default() -> Postgres

Returns the “default value” for a type.

impl Dialect for Postgres

const IDENTIFIER_QUOTE: char = '"'

SQL identifier quote character, e.g. " for Postgres/SQLite, ` for MySQL.

fn write_placeholder(n: usize, out: &mut String)

Writes the placeholder for the nth bound parameter (1-indexed). Postgres numbers them ($1, $2, …); MySQL/SQLite are purely positional (? every time, matched by order of appearance).

const CAST_BIGINT: &'static str = "BIGINT"

How this dialect spells the two types an aggregate is cast back to. CAST itself is standard; the type names are not — MySQL takes SIGNED and DOUBLE where Postgres takes BIGINT and DOUBLE PRECISION.

const CAST_DOUBLE: &'static str = "DOUBLE PRECISION"

const PARENTHESIZED_SET_OP_BRANCHES: bool = true

Whether a set operation’s branches may be parenthesised. SQLite’s grammar has no place for a parenthesised SELECT around UNION.

const INSERT_NO_COLUMNS: &'static str = " DEFAULT VALUES"

How to insert a row that names no column, which is what a table whose every column is generated leaves. INSERT INTO t () VALUES () is MySQL’s spelling and a syntax error everywhere else.

const OFFSET_WITHOUT_LIMIT: Option<&'static str> = None

What to put in a LIMIT when a query has an OFFSET and no limit. Postgres takes a bare OFFSET; SQLite and MySQL don’t, and each spells “no limit” differently.

impl SupportsFullOuterJoin for Postgres

impl SupportsOnConflict for Postgres

impl SupportsReturning for Postgres

impl SupportsRightJoin for Postgres