Struct diesel::pg::types::sql_types::Jsonb
[−]
[src]
pub struct Jsonb;
The jsonb
SQL type. This type can only be used with feature = "serde_json"
jsonb
offers several advantages over regular JSON:
There are two JSON data types:
json
andjsonb
. They accept almost identical sets of values as input. The major practical difference is one of efficiency. Thejson
data type stores an exact copy of the input text, which processing functions must reparse on each execution; whilejsonb
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
FromSql
impls
Examples
extern crate serde_json; #[derive(Queryable)] struct Contact { id: i32, name: String, address: serde_json::Value, } #[derive(Insertable)] #[table_name="contacts"] struct NewContact { name: String, address: serde_json::Value, } table! { contacts { id -> Integer, name -> VarChar, 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" }"#).unwrap(); let new_contact = NewContact { name: "Claus".into(), address: santas_address.clone() }; let inserted_contact = insert(&new_contact).into(contacts) .get_result::<Contact>(&connection).unwrap(); assert_eq!(santas_address, inserted_contact.address);
Trait Implementations
impl QueryId for Jsonb
[src]
impl NotNull for Jsonb
[src]
impl SingleValue for Jsonb
[src]
impl Debug for Jsonb
[src]
impl Clone for Jsonb
[src]
fn clone(&self) -> Jsonb
Returns a copy of the value. Read more
fn clone_from(&mut self, source: &Self)
1.0.0
Performs copy-assignment from source
. Read more