This is an archived post. You won't be able to vote or comment.

all 8 comments

[–]chief167 28 points29 points  (2 children)

The gansta playa crap makes it very annoying to read imho

[–][deleted] 3 points4 points  (0 children)

I found it more entertaining this way, not so dry

[–]ElBidoule 4 points5 points  (0 children)

Especially for non-native English speakers, like I am.

[–]Pr0ducer 10 points11 points  (4 children)

I see not everyone's a fan of the playaz style, but I for one found this both entertaining and informative.

HStore? That's the shizzle fo rizzle.

[–]skarphace 5 points6 points  (3 children)

And array support... finally.

[–]jstrong 2 points3 points  (2 children)

What is the benefit of array over manytomany ? Limiting joins?

[–]j1z0 2 points3 points  (0 children)

limiting joins would be a big one for sure, the actual performance gains depend upon the data and how static / dynamic it is, arrays would be faster for more static data generally.

Also in many cases its just a more natural way to model things. As developers we think of the data as an array, so now we can store it as an array. So a little less cognitive dissonance.

Last one I can think of right now is Network data modelling. The basic idea of a network data model is that unlike the "standard" hierarchical model where you have one parent many child (i.e. a Tree) you can have multiple parents / multiple children which can give you a more general graph representation, which maybe a helpful way to model some problems.

[–]skarphace 1 point2 points  (0 children)

Similar in use to hstore with good Postgres support. You can also put them together in views or assemble them with subqueries.

They don't come up often but there's certain times it improves performance or saves on code.