jsonb

I have a JSONB field that sometimes has nested keys. Example: {"nested_field": {"another URL": "foo", "a simple text": "text"}, "first_metadata": "plain string", "another_metadata": "foobar"} If I do .filter(TestMetadata.metadata_item.has_key(nested_field)) I get this record. How can I search for existence of the nested key? ( "a simple text" ) van With SQLAlchemy the following should work for your test string: class TestMetadata(Base): id = Column(Integer, primary_key=True) name = Column(String) metadata_item = Column(JSONB) as per SQLAlchemy documentation of JSONB (search for Path index

I have a Postgres table that has content similar to this: id | data 1 | {"a":"4", "b":"5"} 2 | {"a":"6", "b":"7"} 3 | {"a":"8", "b":"9"} The first column is an integer and the second is a json column. I want to be able to expand out the keys and values from the json so the result looks like this: id | key | value 1 | a | 4 1 | b | 5 2 | a | 6 2 | b | 7 3 | a | 8 3 | b | 9 Can this be achieved in Postgres SQL? What I've tried Given that the original table can be simulated as such: select * from ( values (1, '{"a":"4", "b":"5"}'::json), (2, '{"a":"6", "b":"7"}'::json), (3, '{"a":"8", "b":"9"}':

...or the question mark question. I am currently implementing the search functionality for a postgres database, in php, that uses the new jsonb type. To achieve this I am executing prepared statements with named placeholders. However I have run into an interesting problem whilst trying to use some of the new postgres JSON containment and existence operators along with named placeholders. The basis of issue being that the operators themselves use the question mark ? as part of their syntax. i.e. ? Does the key/element string exist within the JSON value? ?| Do any of these key/element strings

Suppose that you want to store "tags" on your object (say, a post). With release 9.4 you have 3 main choices: tags as text[] tags as jsonb tags as text (and you store a JSON string as text) In many cases, 3rd would be out of question since it wouldn't allow query conditional to 'tags' value. In my current development, I don't need such queries, tags are only there to be shown on posts list, not to filter posts. So, choice is mostly between text[] and jsonb . Both can be queried. What would you use? And why? Erwin Brandstetter In most cases I would use a normalized schema with a table option

psql --version psql (PostgreSQL) 9.4.1 rails -v Rails 4.2.0 I added a jsonb column through migration like that class AddPreferencesToUsers < ActiveRecord::Migration def change add_column :users, :preferences, :jsonb, null: false, default: '{}' add_index :users, :preferences, using: :gin end end I get this error : PG::UndefinedObject: ERROR: type "jsonb" does not exist LINE 1: SELECT 'jsonb'::regtype::oid any help ? After looking around I discovered that my postgresql version is not 9.4 by running the right command postgres=# SHOW SERVER_VERSION; server_version ---------------- 9.1 So I had

I wondering what will be the right approach to build EAV on jsonb. I have Attribute -> Values tables as like in standard EAV. CREATE TABLE attribute_values ( id INTEGER, attribute_id INTEGER, value VARCHAR(255) ); CREATE TABLE attributes ( id INTEGER, name VARCHAR(255) ); Values will saved in attributes filed of Entity CREATE TABLE entity ( id INTEGER, title TEXT, attributes JSONB ); Tables Attribute created to control duplicate attributes their types and better determine what it's a attribute is. For example to avoid: {weight: 100} and {Weight: 100} or {weigh: 100} . Values for work with