
I am not sure you are going to be happy with our nested transactions.

Your text is:

> (1) embedded transactions
> - i.e. the "outer" transaction can rollback an "inner" committed
> transaction
> - currently the commit of the inner transaction would commit statements
> of the inner and outer transaction.

Are you saying:

	BEGIN;
	...
	BEGIN;
	UPDATE  ...
	COMMIT or ABORT;
	...
	COMMIT;

that you want the UPDATE to commit even if the outer transaction aborts?
I don't plan to have nested transactions work that way.  What will
happen is that if the UPDATE transaction aborts, the outer transaction
will not automatically abort.  Will that help you?

The savepoint version is:


	BEGIN;
	...
	SAVVEPOINT xx;
	UPDATE  ...
	ROLLBACK TO xx;
	...
	COMMIT;

---------------------------------------------------------------------------

Jorg Janke wrote:
> Hi guys,
> 
> The main causes for the Compiere hold are 
> (1) embedded transactions
> - i.e. the "outer" transaction can rollback an "inner" committed
> transaction
> - currently the commit of the inner transaction would commit statements
> of the inner and outer transaction.
> (2) the lack of 'proper' PL/SQL Procedure support (a big inconvenience,
> not the show stopper)
> compared with what DB/2 and Oracle provides.
> 
> Compiere developed a "Oracle to PostgreSQL" online and offline converter
> - i.e. in goes the Oracle or DB/2 syntax, out comes the PostgreSQL
> syntax. Initial documentation at
> http://www.compiere.org/technology/pg/porting.html - see also source
> code API documentation of the "dbPort" module in Compiere.
> 
> We plan to discontinue the above porting kit.  Our current plan is to
> use Java CMP (Container Managed Persistency) - i.e. transaction
> management in Java for complete database independence with databases
> with a JDBC 3.0 driver.
> 
> Cheers,
> 
> Jorg Janke      (203) 445-9503                   http://www.compiere.org
> Smart ERP & CRM Business Solution for Distribution and Service  globally
> ------------------------------------------------------------------------
> General questions/issues:   http://sourceforge.net/forum/?group_id=29057
> Support via:  http://sourceforge.net/tracker/?group_id=29057&atid=410216
> ------------------------------------------------------------------------
> 
> 
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us] 
> Sent: 01 December, 2002 17:45
> To: Justin Clift
> Cc: PostgreSQL Hackers Mailing List; Jorg Janke
> Subject: Re: [HACKERS] Does anyone know what "embedded transactions"
> are?
> 
> 
> Justin Clift wrote:
> > Hi guys,
> > 
> > Was just looking at the project page for Compiere, an Open Source
> > ERP+CRM solution that is usually in the top 10 most popular 
> > ERP+SourceForge
> > projects.
> > 
> > They were attempting to port Compiere from Oracle to PostgreSQL, but 
> > have stopped (apparently) because PostgreSQL doesn't support "embedded
> 
> > transations".
> > 
> > http://www.compiere.org/technology/independence.html
> > 
> > Does anyone know what they're talking about?
> 
> I assume it is:
> 
> 	BEGIN;
> 	...
> 	BEGIN;
> 	...
> 	COMMIT;
> 	COMMIT;
> 
> That thing I am trying to do for 7.4.
> 
> -- 
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman@candle.pha.pa.us               |  (610) 359-1001
>   +  If your life is a hard drive,     |  13 Roberts Road
>   +  Christ can be your backup.        |  Newtown Square, Pennsylvania
> 19073
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Thu, 5 Dec 2002 01:17:03 -0500 (EST)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: Compiere "embedded transactions"