george stewart [EMAIL PROTECTED] writes:
Date: 18 Mar 2003 09:07:06 -0500
From: george stewart [EMAIL PROTECTED]
Reply-To: Jakarta Commons Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [resources]ResourceBundle.getBundle
In the messages class, there's static
In the messages class, there's static method:
public static Messages getMessages(String name)
which does this:
Resources resources = factory.getResources(name + .LocalStrings);
This doesn't work for ResourceBundle.getBundle on W2K with JDK 1.3.1_04.
You could use name of the form name +
getMoreResults() precedes getResultSet().
Using this is slightly more efficient than an update followed by a query.
Another thing I wanted to mention is that it seems you should have two visible
interfaces to users, one for how to act on a result set and another for retrieving
objects from
Hi,
getMoreResults must precede getResultSet.
It's not big deal, but safes a round trip to db server in case that you're using
identity.
I have comment on your interfaces.
It's seems that you should have 2 interfaces, one for what to do with the result set
and another for retrieving the
Juozas Baliuka [EMAIL PROTECTED] writes:
getMoreResults() precedes getResultSet().
Using this is slightly more efficient than an update followed by a query.
JDBC documentation says I must to call getMoreResults() after
getResultSet().
I have no way to test this stuff, doe's some
Juozas Baliuka [EMAIL PROTECTED] writes:
Do you know some use case for this ?
As I understand it must look like this:
ResultSet last = null;
try{
if (pstmt.execute()) {//it can be update or select
do{
last =
Hi,
Could the developers elaborate on reasons for having package access to the interface
ResultSetHandler?
If this was public, user's could create objects without using the object arrays.
If it ever becomes public, it would be nice to have something like this in the package:
static void
Juozas Baliuka [EMAIL PROTECTED] writes:
It will be public if we will not find better ways to handle resultsets.
Thanks very much for your answer. I'll be watching your changes. Making some
interface public and the ability to fill collections would handle 95% of our work.
I've been looking
