On Wed, Aug 04, 2004 at 09:46:22AM +0800, Christopher Kings-Lynne wrote:
> >Depending on how tense you want to be about Oracle compatibility, we
> >could make people actually write their blocks as above --- that is,
> >the SAVEPOINT and ROLLBACK commands would be a required part of the
> >exception-block syntax. They wouldn't actually *do* anything, but
> >they would make the code look more like its Oracle equivalent. I'm not
> >for this, but maybe someone wants to make the case for it?
>
> So long as I can emulate SQL MERGE with it, I'm happy. ie. I need a
> solution to the 'try update, if no rows changed then insert (unique
> index)' common race condition issue. If I cannot keep looping that
> until it succeeds, then exceptions don't help me...
Honestly, I'd *love* to see a merge command built in, assuming it's not
very difficult. I would think that having the database handle this
internally would be much more performant than using pgsql for it.
> Chris
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
>
--
Jim C. Nasby, Database Consultant [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
