Agreed. I would be very interested in hearing the advantages of
converting a query to an array of structs given you can access rows and
columns from a query "natively".
Aaron
Brian Kotek wrote:
It still just doesn't make any sense to me to translate a query into
an array of structs, when a query essentially IS an array of structs
already. There would be a definite cost to do this, and what would be
the benefit? Is there something I'm missing?
Thanks,
Brian
On 5/30/06, *Barry Beattie* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
something simple: an array of structs, not full blown objects.
eg: student ValueObject
==========
name: string
dob: date
timetable: array'o'structs.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject
of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
