From: | Barry Lind <blind(at)xythos(dot)com> |
---|---|
To: | Kim Ho <kho(at)redhat(dot)com> |
Cc: | pgsql-jdbc-list <pgsql-jdbc(at)postgresql(dot)org>, Fernando Nasser <fnasser(at)redhat(dot)com> |
Subject: | Re: Closing a statement |
Date: | 2003-06-26 17:52:31 |
Message-ID: | 3EFB32DF.3060303@xythos.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Kim,
Yes I agree. In the resultset code we are a little better at this, but
the statement code is lacking these checks, and they should be there.
--Barry
Kim Ho wrote:
> After running the JDBC Compatibility Test Suite, I've found that
> statements aren't actually closed when you use stmt.close(). If you try
> to execute a closed statement, it _should_ throw an SQLException, but
> doesn't.
>
> Besides the freeing of resources (which is already handled in close()
> but m_binds[] should probably be freed as well), certain operations
> should be disallowed.
>
> I was thinking of all set/get/execute operations.
>
> Any suggestions/comments?
>
> Cheers,
>
> Kim
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
From | Date | Subject | |
---|---|---|---|
Next Message | Garrick Dasbach | 2003-06-27 18:44:02 | executeQuery and busy waiting |
Previous Message | Kim Ho | 2003-06-26 17:27:59 | Closing a statement |