From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PgSQL MVCC vs MySQL InnoDB |
Date: | 2004-10-25 19:45:40 |
Message-ID: | 417D57E4.8090300@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/25/2004 2:42 PM, Andrew Sullivan wrote:
> On Mon, Oct 25, 2004 at 01:15:33PM -0400, Jan Wieck wrote:
>> On 10/25/2004 11:53 AM, nd02tsk(at)student(dot)hig(dot)se wrote:
>>
>> >Is this true?
>>
>> From a functional point of view, the two appear to do the same thing.
>
> Well, except for one difference. InnoDB will allow you refer to
> tables not controlled by the InnoDB table handler, whereas we don't
That is a (mis)feature of MySQL itself, not of the InnoDB storage engine
if used in a mixed table type query by MySQL. InnoDB does not control
what is done in the "upper management" with the rows it returns from a
scan. This kind of abuse is as much InnoDB's fault as it is your fault
when your quite accurate work is merge-joined with marketing material
for decision making.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-10-25 19:45:44 | Re: Arrays, placeholders, and column types |
Previous Message | Jeff Davis | 2004-10-25 19:45:19 | Re: The reasoning behind having several features outside |