Struct Jsonb

pub struct Jsonb;

The jsonb SQL type. This type can only be used with feature = "serde_json"

In SQLite, jsonb brings mainly performance improvements over regular JSON:

The advantage of JSONB in SQLite is that it is smaller and faster than text JSON - potentially several times faster. There is space in the on-disk JSONB format to add enhancements and future versions of SQLite might include options to provide O(1) lookup of elements in JSONB, but no such capability is currently available.

In SQLite, JSONB is intended for internal use by SQLite only. Thus, future SQLite updates might break our JSONB implementation. And one might have to wait and then upgrade diesel for those changes to be accounted for. If you do not want this, prefer the regular Json type.

In PostgreSQL, jsonb offers several advantages over regular JSON:

There are two JSON data types: json and jsonb. They accept almost identical sets of values as input. The major practical difference is one of efficiency. The json data type stores an exact copy of the input text, which processing functions must reparse on each execution; while jsonb data is stored in a decomposed binary format that makes it slightly slower to input due to added conversion overhead, but significantly faster to process, since no reparsing is needed. jsonb also supports indexing, which can be a significant advantage.

…In general, most applications should prefer to store JSON data as jsonb, unless there are quite specialized needs, such as legacy assumptions about ordering of object keys.

ToSql impls

• serde_json::Value

FromSql impls

• serde_json::Value

Examples

table! {
    contacts {
        id -> Integer,
        name -> Text,
        address -> Jsonb,
    }
}

let santas_address: serde_json::Value = serde_json::from_str(
    r#"{
    "street": "Article Circle Expressway 1",
    "city": "North Pole",
    "postcode": "99705",
    "state": "Alaska"
}"#,
)?;
let inserted_address = insert_into(contacts)
    .values((name.eq("Claus"), address.eq(&santas_address)))
    .returning(address)
    .get_result::<serde_json::Value>(connection)?;
assert_eq!(santas_address, inserted_address);

Trait Implementations

impl Clone for Jsonb

fn clone(&self) -> Jsonb

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for Jsonb

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

Formats the value using the given formatter.

impl Default for Jsonb

fn default() -> Jsonb

Returns the “default value” for a type.

impl QueryId for Jsonb

const HAS_STATIC_QUERY_ID: bool = true

Can the SQL generated by Self be uniquely identified by its type?

type QueryId = Jsonb

A type which uniquely represents Self in a SQL query.

fn query_id() -> Option<TypeId>

Returns the type id of Self::QueryId if Self::HAS_STATIC_QUERY_ID. Returns None otherwise.

impl SqlType for Jsonb

type IsNull = NotNull

Is this type nullable?

impl CastsTo<Json> for Jsonb

impl CastsTo<Jsonb> for Json

impl CastsTo<Text> for Jsonb

impl Copy for Jsonb

impl FallibleCastsTo<Json> for Jsonb

impl FallibleCastsTo<Jsonb> for Json

impl FallibleCastsTo<Jsonb> for Text

impl FallibleCastsTo<Text> for Jsonb

impl SingleValue for Jsonb