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.
Cal On Thu, Jun 16, 2011 at 2:08 PM, Luke Plant <l.plant...@cantab.net> wrote: > On 16/06/11 13:34, Cal Leeming [Simplicity Media Ltd] wrote: > > Hi all, > ... > > Could someone indicate if there is a reason for this, or if I should be > > filing a bug report? > > As the changeset comment indicates, the snippet you wanted was removed > because it was an internal function that was no longer being used in > Django. Our backwards compatibility promise does not extend to > undocumented internals, so there isn't a bug here. > > 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 django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
