On 16/06/11 14:10, Cal Leeming [Simplicity Media Ltd] wrote: > Okay, er. > > In reference to the original problem (cursor's not default to > DictCursor), thus no field names are returned, is there a specific > reason for this? If not, I'll probably raise a ticket to have it > considered for change.
I'm not sure exactly what you are asking, because this is about default behaviour. The choice of a default is usually made according to what is thought to be the most useful, or according to the way it happens to have been done in the past. I also don't know what exactly you are suggesting. Our backwards compatibility policy means that we aren't going to change the default, unless other people's code is going to work transparently (which wouldn't be the case here), so it doesn't really matter what the original reason was, if there was one. If you are suggesting that we add some functionality to make use of DictCursor more useful, then certainly the suggestion is valid. Regards, Luke -- The probability of someone watching you is proportional to the stupidity of your action. Luke Plant || http://lukeplant.me.uk/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
