On Mon, 9 Jul 2001, Barry Lind wrote:
> Anders,
>
> I have some issues with this patch.
>
> 1) Please don't require the driver to perform yet another round trip to
> the server to get the database encoding. You changed the following code
> which accessed the server once at connection creation:
[
> > I have some issues with this patch.
> >
> > 1) Please don't require the driver to perform yet another round trip to
> > the server to get the database encoding. You changed the following code
> > which accessed the server once at connection creation:
> [snip]
> > 2) I don't like having test
[EMAIL PROTECTED] writes:
> > The list of columns you return is wrong. There is no COLUMN_NAME column.
>
> Does PostgreSQL actually support privileges for individual columns?
No. Even if it would, this would belong into
DatabaseMetaData.getColumnPrivileges(). getColumnPrivileges() could still
Steve Wampler wrote:
>
> Steve Wampler wrote:
> >
> ...
> > Too much data was received.
> > at org.postgresql.PG_Stream.ReceiveString(PG_Stream.java:306)
> > at org.postgresql.Connection.ExecSQL(Connection.java:532)
> > at org.postgresql.jdbc2.Statement.execute(Statement.j
Steve Wampler writes:
> I think I originally saw the problem when an INSERT that included a
> *very* long text field entry generated an exception (I had dropped a
> function used as a trigger on inserts)) - the message that
> comes back from the back end includes (as near as I can remember)
> the
Steve,
In looking at the source code I couldn't explain why you would be
getting the error below. (All of the places that I see a max buffer
size specified, seem to be appropriate and shouldn't generate the error
you are seeing). Can you send a test case to the list for me to
investigate th
Sheer,
If your code only runs against PostgreSQL, then the answer is that it
wouldn't be worth your time. The FE/BE protocol that the postgres JDBC
driver uses doesn't support binding variables, so the JDBC driver ends
up doing exactly what you are currently doing in your code, and builds
up
Barry Lind wrote:
>
> Steve,
>
> In looking at the source code I couldn't explain why you would be
> getting the error below. (All of the places that I see a max buffer
> size specified, seem to be appropriate and shouldn't generate the error
> you are seeing). Can you send a test case to the
I don't think this patch is a good idea because:
a) its only purpose is to supress warning messages in the server log
when the client isn't coded properly (i.e. the client application should
be closing connections gracefully/explicitly before calling exit()).
b) The costs of this patch are gre
Barry Lind wrote:
>
> I don't think this patch is a good idea because:
>
> a) its only purpose is to supress warning messages in the server log
> when the client isn't coded properly (i.e. the client application should
> be closing connections gracefully/explicitly before calling exit()).
For s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10-Jul-2001 Joseph Shraibman wrote:
> Barry Lind wrote:
>> a) its only purpose is to supress warning messages in the server log
>> when the client isn't coded properly (i.e. the client application should
>> be closing connections gracefully/expli
>
> Why do you consider semi colons outside of quotes to be an error
condition?
>
> It is legal under postgresql to execute multiple SQL statements under
> one call to the server. For example you can execute:
>
> update foo set bar = ?; select * from foo;
I agree that it probably is. Unfortunate
PG 7.1.2, jdbc7.1-1.2.jar, RH Linux 6.2 (with upgrade to kernel 2.4.5 [and
library upgrades]):
I've got a table with 5 columns, two of which are type 'text' and intended to
hold XMLized java objects (constructed using the JSX package). However, the
XML tends to be pretty large (and I'll need
13 matches
Mail list logo
