jsonb

I'm experimenting with keeping values like the following in a Postgres jsonb field in Postgres 9.4: [{"event_slug":"test_1","start_time":"2014-10-08","end_time":"2014-10-12"}, {"event_slug":"test_2","start_time":"2013-06-24","end_time":"2013-07-02"}, {"event_slug":"test_3","start_time":"2014-03-26","end_time":"2014-03-30"}] I'm executing queries like: SELECT * FROM locations WHERE EXISTS ( SELECT 1 FROM jsonb_array_elements(events) AS e WHERE ( e->>'event_slug' = 'test_1' AND ( e->>'start_time' >= '2014-10-30 14:04:06 -0400' OR e->>'end_time' >= '2014-10-30 14:04:06 -0400' ) ) ) How would I

根据 Betteridge 定律（任何头条的设问句可以用一个词来回答：不是），除非你的JSON数据很少修改，并且查询很多。 最新版的PostgreSQL添加更多对JSON的支持，我们曾经问过PostgreSQL是否可以替换MongoDB作为JSON数据库，答案显而易见，但我们更希望的是，啊哈，这个问题由读者来问了。 “PostgreSQL不是已经有一些json的支持了吗？” 是的，在PostgreSQL 9.4之前的版本也有JSON 数据类型了，你可以这样： CREATE TABLE justjson ( id INTEGER, doc JSON) >INSERT INTO justjson VALUES ( 1, '{ "name":"fred", "address":{ "line1":"52 The Elms", "line2":"Elmstreet", "postcode":"ES1 1ES" } }'); 保存了JSON的原始文本到数据库，包括空白行和键顺序及重新的键，我们来查看下保存的数据： >SELECT * FROM justjson; id | doc ----+--------------------------------- 1 | { + | "name":"fred", + | "address":{ + | "line1":"52 The Elms",

Looking through the documentation for the Postgres 9.4 datatype JSONB, it is not immediately obvious to me how to do updates on JSONB columns. Documentation for JSONB types and functions: http://www.postgresql.org/docs/9.4/static/functions-json.html http://www.postgresql.org/docs/9.4/static/datatype-json.html As an examples, I have this basic table structure: CREATE TABLE test(id serial, data jsonb); Inserting is easy, as in: INSERT INTO test(data) values ('{"name": "my-name", "tags": ["tag1", "tag2"]}'); Now, how would I update the 'data' column? This is invalid syntax: UPDATE test SET data->

PostgreSQL just introduced JSONB and it's already trending on hacker news . It would be great if someone could explain how it's different from Hstore and JSON previously present in PostgreSQL. What are it's advantages and limitations and when should someone consider using it? pozs First, hstore is a contrib module, which only allows you to store key => value pairs, where keys and values can only be text s (however values can be sql NULL s too). Both json & jsonb allows you to store a valid JSON value (defined in its spec ). F.ex. these are valid JSON representations: null , true , [1,false,

I am working in Postgres 9.4 with the following table: Column │ Type │ Modifiers ─────────────────┼──────────────────────┼────────────────────── id │ integer │ not null default practice_id │ character varying(6) │ not null date │ date │ not null pct_id │ character varying(3) │ total_list_size │ double precision │ not null star_pu │ jsonb │ I have the following query: SELECT date, AVG(total_list_size) AS total_list_size, json_object_agg(key, val) AS star_pu FROM (SELECT date, SUM(total_list_size) AS total_list_size, key, SUM(value::numeric) val FROM frontend_practicelist p, jsonb_each_text(star