From: | snpe <snpe(at)snpe(dot)co(dot)yu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL x Oracle |
Date: | 2003-02-10 22:40:33 |
Message-ID: | 200302102240.33784.snpe@snpe.co.yu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Monday 10 February 2003 15:58, Andrew Sullivan wrote:
> On Mon, Feb 10, 2003 at 03:40:02PM +0100, Fabrizio Ermini wrote:
> > On 9 Feb 2003 at 17:48, Ben-Nes Michael wrote:
> > > also I heard that you cant do transaction within transaction in
> > > postgres while in Oracle you can. ( im not sure if its true at all )
> >
> > nope... "commit" in Oracle close ALL open transaction.
>
> I suspect the point is really that an error inside a transaction in
> Oracle doesn't force you to roll back to the very beginning. I
> believe this is listed as "savepoints" in the current TODO.
>
> Which reminds me of another feature PostgreSQL has. You can buy an
> awful lot of _very talented_ developer time with the fees you'd just
> to use stock Oracle. I don't know why more companies (and to date I
> have to include my own employer in this category) don't spend just a
> little of that savings on PostgreSQL development.
>
Oracle don't get all rows in query - cursors in oracle are out of a transaction
This is important for big queries
regards
Haris Peco
From | Date | Subject | |
---|---|---|---|
Next Message | Brandon Craig Rhodes | 2003-02-10 23:23:56 | "ON INSERT rule may not use OLD" on simple query |
Previous Message | Ed L. | 2003-02-10 22:07:12 | Re: 7.3.2: test select_having ... FAILED |