rüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag von Jason
> Godden
> Gesendet: Donnerstag, 17. Juli 2003 14:23
> An: Daniel Schuchardt; [EMAIL PROTECTED]
> Betreff: Re: [GENERAL] 2 connections 1 transaction
>
>
> Hi Daniel,
>
>
The short answer is - there is no way you can do it.
Different connections in postgres (and in every other DB engine I heard
of) can never share the same transaction.
As far as I can see, the only way to do what you want is to rethink your
architechture so that the clients never talk directly to
On 17 Jul 2003 at 16:47, Daniel Schuchardt wrote:
> 1.Client starts Transaction and does some changes.
> 2.Now the client notices that very huge operations are nescesarry and
> starts a procedure @ App-Server
> 3.App-Server reads the database and makes changes. Problem : the changes
> the client do
stag, 17. Juli 2003 14:23
An: Daniel Schuchardt; [EMAIL PROTECTED]
Betreff: Re: [GENERAL] 2 connections 1 transaction
Hi Daniel,
Maybe make procedural wrappers around all events undertaken and simulate
it?
ie:
1. Client connects to MS SQL Server (Application Server) and PG Server
2. SQL Server con
Hi Daniel,
Maybe make procedural wrappers around all events undertaken and simulate it?
ie:
1. Client connects to MS SQL Server (Application Server) and PG Server
2. SQL Server connects to PG Server aswell
3. Client begins new record process
4. New record process starts by putting PG into serial
