Thanks Kevin, for correcting the example, I actually meant what you have
assumed :)
Also, another question in JDK5 context, the code will be very precise and
type checking/assumptions about types can be avoided in many places in DAS
using JDK5 generics. Other features from JDK5 can be used too.
Below is one of the use cases where user will get some benefit:-
USE CASE:
bigtable{col1, col2,col50}
SIMPLEST CLIENT CODE: WITH NAMED PARAM SUPPORT
Command insertAdhoc = das.createCommand(insert into bigtable values (?, ?,
?...50 times));
insertAdhoc.setParameter(ID, new Integer(6));
This sounds good to me since programming model consistency is so very
important. I agree that partial index specification should *not* be
supported. I was concerned by your example:
Parameters
Parameter name=ID index=1/ -- rest of the attributes optional
Parameter
Hi,
A few days ago there was a user question about passing name in Parameter:-
http://www.mail-archive.com/[EMAIL PROTECTED]/msg19339.html
When checking how Parameters are used in Config, came across the following
points.
There is a difference in Config (SDO) generated Parameter and
The named parameter support was removed from earlier versions of DAS,
here is some previous discussion around the subject [1] See also
tuscany-658. We might need to do further cleanup on the impl, if I
understood correctly.
As for your second suggestion (parameter column types), could you
expose
