[JDBC driver ignores catalog and schema]
On Fri, 07 Sep 2001 09:58:36 -0400, Tom Lane wrote:
I think it'd be a mistake to expend much effort on this issue in JDBC
right now. We will eventually implement SQL92-compliant schemas in the
backend, and once that happens it'll be possible to do
On Sat, 01 Sep 2001 17:43:39 +0200, you wrote:
I've tried the jxdbcon driver now and it gives another view
of the actual database... I am not a PostgreSQL guy so I am
quite confused here. Anyway, this one seems to give the most
appropriate view of the database since the system tables
are listed
On Sun, 09 Sep 2001 14:25:38 +0530, you wrote:
Then, I tried to install the jar file for jdbc 'jdbc7.0-1.2. jar'
and extracted it to the directory /usr/lib/pgsql.
Never extract the contents of these jar files!
http://jdbc.postgresql.org/docs/#install
Put it in your CLASSPATH instead.
7.0 is
I'm not sure if you get this message via the list, but if you
post an a mailing list it would be nice if your address worked.
- Transcript of session follows -
... while talking to mail.ceedees.com.:
RCPT To:[EMAIL PROTECTED]
550 [EMAIL PROTECTED]... Relaying denied
550 [EMAIL
On Sun, 09 Sep 2001 14:48:41 +0200, you wrote:
It is of course a performance improvement if it uses only 1 SQL statement
rather than N+1 with N being the number of columns reported. E.g. if you
list all columns of all tables in a big database, this would be a huge win.
I think that can only
Attached is a patch that fixes DatabaseMetaDataTest in the JDBC
driver's test suite. With previous patches applied, this reduces
the number of failures of the test suite from 6 to 4. The patch
fixes the test case itself, rather than the driver.
Details:
1) The driver correctly provided
I can add something if people agree there is an issue here.
I've added a new section Character encoding to
http://lab.applinet.nl/postgresql-jdbc/, based on the
information from Dave and Barry.
I haven't seen a confirmation from pgsql-hackers or Bruce yet
that this issue will be added to
On Sun, 9 Sep 2001 10:24:32 -0400 (EDT), Bruce Momjian wrote:
I can add something if people agree there is an issue here.
IMO the issue is twofold. Without multibyte compiled in:
1) the server cannot tell the client which single byte character
encoding is being used, so a client like JDBC
I've added a new section Character encoding to
http://lab.applinet.nl/postgresql-jdbc/, based on the
information from Dave and Barry.
I haven't seen a confirmation from pgsql-hackers or Bruce yet
that this issue will be added to the Todo list. I'm under the
impression that the backend developers
Rene Pijlman writes:
Currently the JDBC driver says:
- Backend = 7.2 sorts nulls higher than any other value in a
domain. In other words: ascending means nulls at the end,
descending means nulls at the start.
- Backend 7.2 puts nulls at the end regardless of sort order.
That is correct.
On Sun, 9 Sep 2001 15:25:17 +0200 (CEST), you wrote:
That is correct.
Thanks.
Would it be useful to add this information to the documentation,
e.g. the documentation of ORDER BY in SELECT?
Most likely.
I'll post it on the docs list.
Regards,
René Pijlman [EMAIL PROTECTED]
I'm working on a problem in the JDBC driver that's related to
timezones.
How does PostgreSQL handle timezones in the FE/BE protocol
exactly?
When a client sends a time or timestamp value to the server via
the FE/BE protocol, should that be:
1) a value in the client's timezone?
2) a value in the
On Sun, 09 Sep 2001 13:38:52 -0700, you wrote:
[...]
Thanks for your explanation. This helps a lot.
If you could post a bit more about the issue you are having
I might be able to be more specific.
I'm looking at the 4 remaining failures of our own JDBC test
suite. They all have to do with
Your connection url looks funny, it should probably be more like
jdbc:postgresql://localhost/testdb
dave
On Sun, 9 Sep 2001, Larry Rogers wrote:
exception: Exception: java.lang.NullPointerException
Stack Trace:
java.lang.NullPointerException
at
I tried your URL format with the same results. Thanks anyway!
Larry Rogers
On Sunday 09 September 2001 20:15, Dave Weis wrote:
Your connection url looks funny, it should probably be more like
jdbc:postgresql://localhost/testdb
dave
---(end of
Added to TODO.
Bruce,
I think the TODO item should be:
Ability to set character set for a database without multibyte enabled
Currently createdb -E (and the corresponding create database sql
command) only works if multibyte is enabled. However it is useful to
know which single
Larry,
Shouldn't your connection URL be:
jdbc:postgresql://localhost:5432/testdb
instead of
jdbc:postgresql://localhost:5432?database=testdb
thanks,
--Barry
Larry Rogers wrote:
Hi all,
I'm having trouble opening a database connection to a test database on a
fresh PostGreSQL 7.1.3
General backend issue.
--Barry
Bruce Momjian wrote:
Is this a jdbc issue or a general backend issue?
Bruce,
I think the TODO item should be:
Ability to set character set for a database without multibyte enabled
Currently createdb -E (and the corresponding create database sql
command)
18 matches
Mail list logo
