> > Finally, the order and contiguous position of columns may be
> important
> > in some databases when defining multi-column indexes and/or
> > multi-column foreign keys.
>
> I am not aware of any limitations like this in any database server
> I've
> used. I would think that would be a bigger flaw than CFMX's not
> returning
> the fields in the specific order we'd prefer.
>
I ran into it somewhere -- maybe it was composite keys -- there was a
requirement (or a recommendation for efficiency) that the multiple
columns be contiguous and in sequence -- I'll google around some more
and see if I can refresh my memory
Could have been a restriction on an older db system -- anywhere from
DL/I, dBase, etc to present day systems
Or could have been related to one of Joe Celko's manipulations.
I actually think it applied to SQL-Server 6.5 and was a performance
thing when specifying multi-column indexes indexes.
> All that said, I think I'd prefer to receive the field names in the
> order in
> which they're specified, if only for the reason that I find that more
> appealing.
Yeah, really -- there doesn't seem to be a good reason not to,
Select a,,b,c ---- return in order requested
Select * --- return in order defined
On those DBs/drivers where you can access the schema it is less of a
problem -- but you still have to do some extra work.
Dick
"In times like these, it helps to recall that
there have always been times like these."
- Paul Harvey -
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
