Craig Miskell wrote:
> Not trying to be a pain, but custom db attributes are an either/or
> situation (either you have custom db attributes and nothing else, or the
> "standard" method of creating the list of attributes and no custom
> attributes), at least according to my reading of SelectTranslator. Am I
> missing something, is SelectTranslator incorrect in implementation
> (compared to your expectation at least), or are you thinking of something
> else?
Well, actually this was the intended behaviour (even though we haven't
really used this feature so far). The idea is to be consistent. Doing a
"union" of attributes instead of "either/or" introduces some
unpredictability.
Anyway, for prefetches I don't see a big deal with that, since the query
will be built internally and we can do whatever we need (i.e. we can
explicitly add *all* needed DbAttributes as "custom").
Andrus
This archive was generated by hypermail 2.0.0 : Fri Feb 28 2003 - 22:23:04 EST