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
.) 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 thoughts around JDBCClient.
I have to say that I
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 thoughts around JDBCClient.
I have
PROTECTED]
Envoyé : lundi 20 novembre 2006 15:46
À : discuss@restlet.tigris.org
Objet : JDBCClient
Hello, all.
I'm trying to use the JDBCClient to connect to a
database in one of my handlers. I use the
JDBCClientHelper to do this, but when I try to get
the
ResultSet from
: discuss@restlet.tigris.org
Objet : JDBCClient
Hello, all.
I'm trying to use the JDBCClient to connect to a
database in one of my handlers. I use the
JDBCClientHelper to do this, but when I try to get
the
ResultSet from the response, I get an SQL
exception:
java.sql.SQLException
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
6 matches
Mail list logo