why even have multiple rows? just jam it all it there! :-D
LOL
But seriously, when using an ORM to stuff an object hierarchy into a
database, you usually get problems with class inheritance, and all
solutions suck more or less (ie, you get a zillion tables, with assorted
pile of JOINs,
On Tue, May 10, 2011 at 3:32 PM, Merlin Moncure wrote:
> why even have multiple rows? just jam it all it there! :-D
Exactly, serialize the object and stuff it into a simple key->value
table. Way more efficient than EAV.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.
On Tue, May 10, 2011 at 12:56 PM, Pierre C wrote:
>
> While reading about NoSQL,
>
>> MongoDB let's you store and search JSON objects.In that case, you don't
>> need to have the same "columns" in each "row"
>
> The following ensued. Isn't it cute ?
>
> CREATE TABLE mongo ( id SERIAL PRIMARY KEY, o
