Re: default value for set in :db-info?

Thanks!

At the risk of opening a couple cans of worms, why does :immediate  
imply :set nil? It would seem that the :immediate thing would be useful  
in populating instances as it would obviate the need for a db round  
trip. I assume that in :deferred mode, there's a separate round trip  
for each instance? It would seem like it would be a big win to populate  
the join slots for the instances when a query is generated on the  
class, even if the value of the join slot is a set, not a single row.  
Does this make sense or am I missing something about how all of this  
works?

Thanks again,

Cyrus

On Jan 5, 2005, at 9:26 AM, Kevin Rosenberg wrote:

> Cyrus Harmon wrote:
>> It looks to me like the default value for :set is nil. The docs say
>> it's T. Is this a documentation error, should the default really be T,
>> or am I just mistaken about the whole thing?
>
> If you're ever wondering about what CLSQL should do, look at the
> documentation for CommonSQL.
>
> http://www.lispworks.com/documentation/lw44/LWRM/html/lwref 
> -441.htm#pgfId-888283
> shows the default value of :set is t. The page also shows that if
> :retrieval is :immediate, then set will be nil.
>
> I've updated the code in CLSQL to be comply with this and have
> released version 3.1.5 with this fix.
>
> Thanks,
>
> Kevin
>
>
> 	
> -- 
> Kevin Rosenberg
> kevin-HJRc7zDS/[email protected]