diesel 2.4.0

A safe, extensible ORM and Query Builder for PostgreSQL, SQLite, and MySQL
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

//! Types and functions related to PG's and Sqlite's `ON CONFLICT` clause
//!
//! Upsert is currently supported by diesel for the following database systems:
//!
//! * PostgreSQL version 9.5 or newer
//! * Sqlite3 version 3.24.0 or newer
//! * MySQL version 5.7 or newer
//!
//! See [the methods on `InsertStatement`](crate::query_builder::InsertStatement#impl-2)
//! for usage examples.
//!
//! Constructing an upsert statement from an existing select statement
//! requires a where clause on sqlite due to a ambiguity in their
//! parser. See [the corresponding documentation](https://www.sqlite.org/lang_UPSERT.html)
//! for details.
pub(crate) use self::on_conflict_extension::OnConflictHelper;
use crate::query_builder::upsert::on_conflict_actions::Excluded;

mod on_conflict_extension;

#[doc(inline)]
pub use self::on_conflict_extension::{
    DecoratableTarget, IncompleteDoUpdate, IncompleteOnConflict,
};
#[cfg(feature = "postgres_backend")]
pub use crate::pg::query_builder::on_constraint::*;

/// Represents `excluded.column` in an `ON CONFLICT DO UPDATE` clause,
/// and `VALUES(column)` for MySQL and MariaDB.
pub fn excluded<T>(excluded: T) -> Excluded<T> {
    Excluded::new(excluded)
}

/// Reexports `excluded` as `values` for MySQL and MariaDB using
/// `VALUES(column)`, which MySQL deprecates but whose replacement requires MySQL 8.0.19.
#[cfg(any(feature = "mysql_backend", feature = "mariadb_backend"))]
pub use excluded as values;