From: | Ned Wolpert <wolpert(at)yahoo(dot)com> |
---|---|
To: | "Kovcs_Pter" <peter(dot)kovacs(at)sysdata(dot)siemens(dot)hu> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Submittal for JDBC Pooling driver (For 7.3) |
Date: | 2002-01-02 20:36:04 |
Message-ID: | 20020102203604.23341.qmail@web13404.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
(I'm replying using the thread-name you wanted.)
--- Kovcs_Pter <peter(dot)kovacs(at)sysdata(dot)siemens(dot)hu> wrote:
> My main point with my post was to clarify that there are no outstanding
> legal issues with the Exoffice contribution. I am not very familiar with
There are no legal issues to worry about. Exoffice (now known as
Intalio's
exolab project) code was/is BSD-based licensed, which is completely
integrated to the driver. So no worries there.
> Also, if support for this kind of functionality (transaction support --
> even if it is limited to isolated ("local") transactions) is
discontinued
> as part of PostgreSQL, for purely efficiency reasons I would have to
I feel confident in saying the following: (Disclaimer, I'm not a
CVS committer, just a code submitter.)
Transaction support in PostgreSQL will _never_ be discontinued. Ever.
If it ever does, many people will migrate away from from PostgreSQL.
If anything, transaction support will be expanded, so no worries here
either.
> Where do you see incompleteness in the code? Does this incompleteness
> relates to functionality relevant to PostgreSQL?
XA support is incomplete simply because PostgreSQL doesn't support
two-phase commits. How can one test it otherwise? TP monitors aren't
that useful with a database that only works in (as you say) 'local'
mode for transactions.
> for (which aspects of the jdbc2 extensions they're cover). The only
> extension these classes do not support seem to be RowSets. Since this
> package does not contain a class named 'RowSet' (or even close to it)
Yes. I'm planning to work on rowsets once I get the pooling stuff
complete. It would be great if you wanted to help on that too. (And
anyone else, for that fact)
Note that I don't think the current Pooled API connections are complete
either. The api is there, but the functionality behind the api is
not correct. (Example, if a SQL error occurs, ConnectionEventListeners
are not informed)
=====
Virtually, | "Must you shout too?"
Ned Wolpert | -Dante
wolpert(at)yahoo(dot)com |
_________________/ "Who watches the watchmen?"
4e75 -Juvenal, 120 AD
-- Place your commercial here -- fnord
__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Kovács Péter | 2002-01-02 21:22:16 | Re: Submittal for JDBC Pooling driver (For 7.3) |
Previous Message | Kovács Péter | 2002-01-02 20:12:15 | Re: What happend to the Exoffice XA package? |