XML, HSTORE, JSON, JSONB - OH MY!
Formal Metadata
| Title | XML, HSTORE, JSON, JSONB - OH MY! |
|
| Alternative Title | HSTORE, XML, JSON, JSONB OH MY! |
|
| Title of Series | |
| Number of Parts | 31 |
| Author | |
| Contributors | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Ottawa, Canada |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Use the unstructured data type that's right for you.
PostgreSQL 9.4 adds a new unstructured data type, JSONB, a variant of JSON optimized for storing objects. JSONB complements the existing XML and JSON document objects, as well as HSTORE. Which one is right for you? We'll take a tour of the features of each, and their advantages and disadvantages for various use cases, all illustrated with real-world examples.
There has been a lot of work on the representation of unstructured data in PostgreSQL, culminating in the addition of the JSONB type in the forthcoming 9.4 release. JSONB complements the existing HSTORE, XML, and JSON types, not to mention arrays. With so many options, which do you use? As usual it depends on your use case.
In this presentation, we'll review the unstructured data types in PostgreSQL, and look at their advantages and disadvantages for:
Document storage
Configuration management
A "schemaless database"
Object serialization
Entity/Attribute/Value models
Path queries |
|
