Jerome,
> Hmm... :-) I believe that my latest checkings
> (earlier today) completely
> removed the finally block. The connection can be
> closed via the
> JdbcResult.release() method. Let me know if I missed
> something.
>
You're right. I've been looking at the previous
version :-(
I'll build i
Hi Kyrre,
> I saw that you had checked in a fix in SVN for the
> issue I reported. The fix does not fix my problem,
> however.
Hmm... :-) I believe that my latest checkings (earlier today) completely
removed the finally block. The connection can be closed via the
JdbcResult.release() method. Let
mer) that
> will facilitate the task of transforming the JDBC
> XML resultsets (or any XML
> document) into a representation (XML, HTML, etc.)
> suitable for the clients.
>
> Stay tuned!
> Jerome
>
> > -Message d'origine-
> > De : Kyrre Kristiansen
&
, etc.) suitable for the clients.
Stay tuned!
Jerome
> -Message d'origine-
> De : Kyrre Kristiansen [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 24 novembre 2006 10:24
> À : discuss@restlet.tigris.org
> Objet : RE: Re: JDBCClient
>
> Hi.
>
> Just some thoug
Hi.
Just some thoughts around JDBCClient.
I have to say that I was a bit surprised when I saw
the implementation of JDBCClient as it is.
What I had envisioned was an implementations that used
a basic mapping from methods to SQL keywords, eg
SELECT, INSERT, UPDATE and DELETE (CRUD, remember?),
w
Hi John,
> I have some concerns about the proposed approach...
>
> (A) What about results that are quite large? I.e. that take up a lot
> of memory or won't fit into memory?
One major use case I see for this JDBC connector is to fetch a reasonable
amount of data in order to assemble a represent
On 11/23/06, thierry boileau <[EMAIL PROTECTED]> wrote:
[...]
Good morning,
you're right : the current behaviour is bugged. If you want to use the
resultSet, the connection need to stay open.
This connector has been released a long time ago and has probably been
updated without tests.
As Jerome
Hello Kyrre,
you're right : the current behaviour is bugged. If you want to use the
resultSet, the connection need to stay open.
This connector has been released a long time ago and has probably been
updated without tests.
As Jerome said, we are working on some refactorings to the JDBC Client in
Hello, again.
I think I might have found the problem. I might have
misread the code completely, but here's what I think
is the case.
In JDBCHelper.handle(), the connection is closed in a
finally-block, before we get a chance to get a hold of
the ResultSet, and hence we get the exception I
mention
9 matches
Mail list logo
