|
Home > Archive > PostgreSQL JDBC > November 2005 > XADataSource interface
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
XADataSource interface
|
|
|
|
| Dave Cramer 2005-10-27, 8:07 am |
| Heikki,
I will look at this shortly, is this a diff from a relatively current
HEAD ?
Dave
On 25-Oct-05, at 1:01 PM, Heikki Linnakangas wrote:
> Hello,
>
> I posted an updated version of the XADataSource implementation few
> weeks ago, but haven't received any comments:
>
> http://archives.postgresql.org/pgsq...09/msg00131.php
>
> Has anybody looked at it yet?
>
> - Heikki
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
| |
| Heikki Linnakangas 2005-10-27, 5:29 pm |
| Thanks. Yes, it's a diff from HEAD. Just checked, it still applies
cleanly.
It only modifies build.xml, everything else is in new files, so it
shouldn't bit rot easily anyway.
On Wed, 26 Oct 2005, Dave Cramer wrote:
> Heikki,
>
> I will look at this shortly, is this a diff from a relatively current HEAD ?
>
> Dave
> On 25-Oct-05, at 1:01 PM, Heikki Linnakangas wrote:
>
>
>
- Heikki
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
| |
| Heikki Linnakangas 2005-10-30, 8:23 pm |
| On Sun, 30 Oct 2005, Chris Smith wrote:
> Heikki Linnakangas wrote:
>
> I didn't look too closely at the patch... but the API docs for Object.equals
> say clearly that this shouldn't be a problem. For any non-null reference x,
> x.equals(null) should evaluate to false. I suspect that the correct solution
> to this problem is to fix the implementation of equals, and not to add a
> check against null where you did.
True. However, since the object is supplied by the transaction manager
implementation, which we have no control over, I'd say it's better to
not make any assumptions about it that we don't have to.
- Heikki
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
| |
| Kris Jurka 2005-10-31, 3:24 am |
|
On Sun, 30 Oct 2005, Heikki Linnakangas wrote:
> The failures at testRecover and testRollback were because
> PGXAConnection.rollback method called Xid.equals with null argument.
> I added a null-check for that, see attached patch.
Applied. I'll put out a new dev release with the xa patches later
tonight. Can you clarify what does/doesn't work in xa for the docs?
> I didn't understand this part of your patch:
>
Well, that's why I emailed you guys. I was initially thinking that the
currentXid shouldn't be disassociated from the xaconnection until a new
transaction was actually started and it could simply commit/rollback the
underlying connection if a new one wasn't started. I see that's not the
case now.
Kris Jurka
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
| |
| Heikki Linnakangas 2005-11-03, 8:28 pm |
| On Mon, 31 Oct 2005, Kris Jurka wrote:
>
>
> On Sun, 30 Oct 2005, Heikki Linnakangas wrote:
>
>
> Applied. I'll put out a new dev release with the xa patches later tonight.
> Can you clarify what does/doesn't work in xa for the docs?
Thanks!
English is not my native language, so please check spelling:
"
The JTA specification requires an XADataSource implementation to
support transaction interleaving (see JTA spec section 3.4.4). However,
since PostgreSQL server doesn't support it natively, the JDBC driver
cannot support it either. The same goes for suspend/resume.
In practice, transaction managers don't need transaction interleaving or
suspend/resume to function correctly. Some commercial databases
also don't implement them natively, but emulate them in the JDBC driver.
That's error prone; PostgreSQL driver will throw an XAException instead.
"
The docs should also include instructions for using the XADataSource.
Example configurations for various application servers would be a nice
too.
- Heikki
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
|
|
|
|
|