* Ned Wolpert <[EMAIL PROTECTED]> wrote:
| Humm... are you saying that the class PostgresqlDataSource doesn't work? I
| guess I'm not sure what doesn't work with the driver. (Course, I've been using
| PoolMan as the datasource to wrap the postgresql default connection rather than
| using the da
Ned,
This is a community of volunteers. So if someone wants to work on JDBC3
that is fine. We don't have the option of telling people how they
should spend their time.
But I agree that jdbc2 still has a bunch of stuff that could be done.
Although much if what remains undone isn't required b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26-Oct-2001 Barry Lind wrote:
> This is a community of volunteers. So if someone wants to work on JDBC3
> that is fine. We don't have the option of telling people how they
> should spend their time.
My bad. I didn't mean to alienate. Sorry i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, I understand.
So, why are people talking about support for JDBC3 where JDBC2 support isn't
even there?
On 26-Oct-2001 Barry Lind wrote:
> Ned,
>
> It may or may not work. That file hasn't been changed in a long time,
> so I doubt anyone is u
Ned,
It may or may not work. That file hasn't been changed in a long time,
so I doubt anyone is using it and therefore it may no longer work.
I don't want to give people the false impression that the javax.sql set
of extensions to JDBC2 is supported by the jdbc driver by providing a
jdbc7.2-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Humm... are you saying that the class PostgresqlDataSource doesn't work? I
guess I'm not sure what doesn't work with the driver. (Course, I've been using
PoolMan as the datasource to wrap the postgresql default connection rather than
using the datas
Ned,
There really isn't a j2ee driver for postgres. If you build the j2ee
driver it is essentially the same as the j2se driver. So I don't see
any reason to confuse people by letting them think there really is a
difference by having two different java2 drivers to choose from on the
web site
