Re: [PATCHES] Thread configure flag

2003-06-19 Thread Peter Eisentraut
Bruce Momjian writes: > First, ecpg has actual thead creation function calls, so I believe we > will still need a --with-threads configure option, at least to control > ecpg, unless we make threading some kind of ecpg runtime flag. This is not an issue because it only affects the libecpg library.

[PATCHES] Allow setObject(x,y,Types.INTEGER) if y is Boolean & added Booleanto SQL Keywords

2003-06-19 Thread Kim Ho
Problem: - Boolean not on list of SQLKeywords (The JDBC CTS seems to think that it should be) - setObject(x,y,Types.INTEGER) will throw exceptions if y is a Boolean. Fix: - Added Boolean to Keywords list. - Added check in setObject() under Types.INTEGER to check if a boolean is passed. True=1.

[PATCHES] Fix setObject() with java.sql.Types.Date/Time/Timestamp

2003-06-19 Thread Kim Ho
Problem: - Error if user attempts to call: 1. setObject(x,y,java.sql.types.Timestamp) if y is a Date 2. setObject(x,y,java.sql.types.Time) if y is a Timestamp 3. setObject(x,y,java.sql.types.Date) if y is a Timestamp 4. setObject(x,y,java.sql.types.Date/Timestamp/Time) if y is a string with valid

[PATCHES] Add checking in setMaxRows, setQueryTimeout, and setFetchSize

2003-06-19 Thread Kim Ho
Problem: - If you try to setMaxRows(), setQueryTimeout() or setFetchSize() to negative values, it should throw an exception, but doesn't. JDBC CTS test failures. Fix: - Added new error messages to errors.properties file. - PSQLExceptions thrown when user attempts to set negative values. Cheer

[PATCHES] pg_hba.conf.sample

2003-06-19 Thread Andrew Dunstan
Here's a small patch to pg_hba.conf.sample that explains the use of CIDR addresses.   I'm still working on a patch to the regular docs.   cheers   andrew sample.patch Description: Binary data ---(end of broadcast)--- TIP 8: explain analyze is

[PATCHES] Patch to be verbose about being unable to read ~/.pgpasss...

2003-06-19 Thread Sean Chittenden
Howdy. Quick chump patch: if libpq finds a ~/.pgpass but can't stat it, print something to stderr letting the user know. If someone went out of their way to put a .pgpass file in place, if they can't read it, it seems worth while to alert them to the fact that it's not being used (ex: root create

Re: [PATCHES] Patch to be verbose about being unable to read ~/.pgpasss...

2003-06-19 Thread Tom Lane
Sean Chittenden <[EMAIL PROTECTED]> writes: > Howdy. Quick chump patch: if libpq finds a ~/.pgpass but can't stat > it, print something to stderr letting the user know. Isn't this gonna complain when the file doesn't exist at all? regards, tom lane --

Re: [PATCHES] Patch to be verbose about being unable to read ~/.pgpasss...

2003-06-19 Thread Sean Chittenden
> > Howdy. Quick chump patch: if libpq finds a ~/.pgpass but can't stat > > it, print something to stderr letting the user know. > > Isn't this gonna complain when the file doesn't exist at all? *blush* Not with the attached patch. -sc -- Sean Chittenden Index: fe-connect.c =