News for hackers. Stuff that matters.
Re: PostgreSQL vs MySQL: an apples to oranges comparison by dscrd on Sunday September 09, 2012 @07:41AM (#4495564)
Are there any books out there that describe how to efficiently use PostgreSQL's object-relation techniques?
Re: PostgreSQL vs MySQL: an apples to oranges comparison by einhverfr on Sunday September 09, 2012 @09:10AM (#4495690)
I am actually thinking of writing one. My blog (yes I am the author of the article, http://ledgersmbdev.blogspot.com) is basically running a fairly large series on these features.

The big thing to realize is that there are two aspects here: development efficiency and complexity cost on one hand, and db performance on the other. A lot of the O/R capabilities really do have a significant complexity cost and it is easy to code solutions that don't work very well performance-wise or otherwise.

In a bit over a week, I will have general recommendations out on the blog entry. As a brief preview:

1: table methods are generally good

2: nested storage is generally bad

3: table inheritance is frequently used for the wrong things. It is a very powerful technique if you think in terms of composition, but not so great if you think in terms of inheritance.

4: avoid to the extent you can putting tuples in columns. Postgres gets really weird in these cases.

Re: PostgreSQL vs MySQL: an apples to oranges comparison by dotborg on Sunday September 09, 2012 @08:09AM (#4495595)
postgres docs are full of performance tips
Re: PostgreSQL vs MySQL: an apples to oranges comparison by joedoe55555 on Sunday September 09, 2012 @02:20PM (#4496471)
I learned SQL with Postgres docs ;)