4 ms·
Postgres Array/Hstore/JSON datatypes have made my Rails apps way simpler. Great combination.
by andyl 13y ago
Postgres Array/Hstore/JSON datatypes have made my Rails apps way simpler. Great combination.
- zen_boy 13y agoCare to expand how? Curious as a Rails developer myself.
- netghost 13y agoIf you just want some background, I actually gave a talk about hstore, arrays, and FTS in postgres for rails devs a few months ago. Links to the talk, slides, sample code, and some follow up articles: http://monkeyandcrow.com/blog/postgres_railsconf2013/ http://monkeyandcrow.com/blog/postgres_railsconf2013/
- dalyons 13y agoI was in the audience! It was a great session - you're a funny guy, explained the concepts well, and there was some really interesting real(or alternate :p) world use-cases for all this stuff.
- zen_boy 13y agoGreat stuff! Seems like the store_accessor works with the :json column type out of the box as well. Throw in a JSON schema validator and we have full-blown validations for :hstore and :json!
- eksith 13y agoI'd love to know how you've set things up [ if you don't mind me prying ;) ]. It would be interesting to see someone else's approach.
- andyl 13y agoWhat I did: 1) Use the latest Postgres (9.3) 2) use Rails4 - this provides String/Integer Arrays, HStore, UUIDs out of the box 3) use post_json (https://github.com/webnuts/post_json https://github.com/webnuts/post_json). These tools made it simpler to do things like tagging, user-defined data attributes, hierarchical data, flexible configuration data. It was always possible to store much of this data using text fields and JSON.parse (or some such), but the new Postgres stuff makes the flexible datatypes queryable. And as built-in support for flexible data types comes online, you can throw away your custom serializers. There's other Postgres datatypes that I haven't used - for geocoding/geosearching, network addresses, etc.
- ddorian43 13y agoWhat is missing the a way to update specific fields in json/hsotre columns, or is there a way ?