From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Kaarel <kaarel(at)future(dot)ee> |
Cc: | <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: Which database part 2 |
Date: | 2003-06-16 18:42:05 |
Message-ID: | Pine.LNX.4.33.0306161239480.2361-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
On Fri, 13 Jun 2003, Kaarel wrote:
> I have been reading a little documentation and mail-lists from both
> sides. I noticed one interesting thing about MySQL: there are different
> table types with different properties. Why doesn't PostgreSQL have
> differently oriented/optimized table types? I found particularly
> intresting the heap table type which is being stored entirely in memory
> not on disk drive.
any points I would have had have been addressed by other folks except for
one.
In MySQL if you define one table of MyISAM (non-transactable) and one of
innodb (transactable) and you do this:
begin;
update myisamtable set field='value' where id=2;
update innodbtable set field='value' where id=2;
rollback;
you now have one table that updated and one that didn't.
I don't consider that a feature.
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2003-06-16 19:11:48 | Re: Which database part 2 |
Previous Message | scott.marlowe | 2003-06-16 18:38:30 | Re: Which database part 2 |