Problem:
- Closing a statement should cause it to throw exceptions when
execute/set/get methods are called on it.
Fix:
- Flag is set when the statement is closed. It is checked whenever an
execute/get/set method is called.
Cheers,
Kim
? cloudscape.LOG
Index: org/postgresql/errors.properties
Oops. Forgot to attach it last time.
On Mon, 2003-06-30 at 12:44, Barry Lind wrote:
> Kim,
>
> Are you going to be submitting a patch for this?
>
> thanks,
> --Barry
>
>
> Kim Ho wrote:
> > On Wed, 2003-06-18 at 13:09, Kim Ho wrote:
> >
> >>Pr
On Wed, 2003-06-18 at 13:09, Kim Ho wrote:
> Problem:
> - setObject(x,y,Types.BIT) throws an exception if y is a Number
> - getObject() on a bit column will return null instead of True or False
> Boolean objects
>
Added Problem:
- Doesn't set bit columns
> Fix:
>
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
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
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.
