Why "json" and not "jsonb" about marten HOT 6 CLOSED

@jeffdoolittle At pretty well the exact time you posted this, I was having a conversation w/ @CoreyKaylor about exactly that. I'm going to switch to jsonb tomorrow morning and see if I can drop the "CAST" 's I have to do w/ the JSON type to query w/ anything that's not a string.

from marten.

or belay that, jsonb worked as is, but I'm still gonna try to optimize the queries for jsonb tomorrow.

from marten.

That sounds great. I'd be interested in contributing as the project progresses as well. I was thinking about building a very similar project and then I saw you create this repo and I thought "why duplicate effort?" :)

from marten.

Also, I'm curious if you saw this blog post series from @robconery - there are some interesting ideas about querying and indexing:

http://rob.conery.io/2015/08/20/designing-a-postgresql-document-api/
http://rob.conery.io/2015/08/21/postgresql-document-api-part-2-full-text-search-and-bulk-save/
http://rob.conery.io/2015/08/25/postgresql-document-api-part-3-finding-things/
http://rob.conery.io/2015/09/01/postgresql-document-api-part-4-complex-queries/

from marten.

@jeffdoolittle Just added you to the gitter room for this. I'd happily take all the help we could get.

https://gitter.im/JasperFx/Marten?utm_source=share-link&utm_medium=link&utm_campaign=share-link

from marten.

Gonna close this one because we are on JSONB now;)

from marten.