Hi again, On Friday 26 April 2013, Anssi Kääriäinen wrote: > [...] > In almost every case it is better to try to minimize the amount of > queries than the amount of loaded fields. The cases where you have > deferred multiple fields, need only one of them later on, and there is > a field that you can't load due to potentially huge value are > hopefully rare. > > But, I don't really care too much. If the objects come from DB queries > instead of something like the use case of Adrian then if you end up > doing deferred field loading you have already failed.
LOBs in Oracle always require at least a separate fetch operation to read them. Thus, you get an extra database hit per field (per record). Getting them before they are needed is almost always inefficient. As I already noted in this thread, they can even get in the way of query execution if not deferred. I think it would be better if, at least on Oracle, such fields could be deferred by default. We are considering achieving this with an introspective custom manager, applied to all models (or at least all models with TextFields) in our project. If I could do it with a special field type, I would, and I'd recommend every other user do the same. Just a data point for this discussion, Shai. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
