Cedric Beust wrote:
>
> Actually, it's more complicated than that, and there are a bunch of reasons why
> Ian's suggestion can't work right now. It would require some drastic changes to
> JDBC (multivalued ResultSets) and/or the way SELECT works in SQL.
Surely there's no need to change JDBC? The JDBC statement to do this is:
ResultSet rs = s.executeQuery("SELECT primKey,
description, date FROM ImageDB WHERE..."")
The trick that EJB QL can't yet pull off is to map rs into a collection of value
objects such as:
public class ImageInfo implements java.io.Serializable
{
public String primKey;
public String description;
public java.util.Date date;
}
However I can't see any fundamental reason why something like this would not
work.
> I've always thought that SELECT was a poor choice for a name. SELECT does not
> actually select something from somethign else, it merely specifies the type of
> what's returned, and this applies to both EJB QL and SQL. It has to be a
> scalar, and there is no way around that. Maybe this will change in the future,
> but until then, I think it will be the vendors' role to provide extensions
> allowing what you're asking.
OK, well I'd urge that the extension be provided soon.
========================================
Ian McCallion
Alexis Systems Limited
Romsey, UK
Tel: +44 1794 514883
Fax: +44 1794 501692
========================================
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
