Patch database documentation to explain how to return fetchall() as a dict rather than list.

[Cal Leeming]

Full discussion about this topic can be found in:

​http://groups.google.com/group/django-developers/browse_thread/thread/72c91698cba2ea5b

So far we have +2 votes and -1 vote.

-1 vote:

The thing is, this is a DB API snippet, not a Django snippet 
specifically.  If Django were a DB API toolbox, then it might make 
sense to include it in some form or other.  But it's not, so in the 
interest of keeping things relatively tidy I'm a -0 on this. 

+2 vote:

It is often said here that Django ORM is designed to do 80% of the 
stuff, the rest can be done using raw SQL. So, giving pointers to 
users how to perform the raw SQL as painlessly as possible is 
something Django documentation should do. 

Could we get some more feedback on this??

Cal

[Brillgen Developers]

+1 - I don't personally have a need for this particular case yet, however I would support having more documentation as long as it met the quality and style guidelines of the project.

Django does provide and mention a way of getting raw db access, this documentation makes sense to put there. It couldn't really hurt.

[Jacob]

There's almost never a reason not to add something to the docs as long as its done in a sensible way. Cal, can you work up a patch with some suggested language and find a good place to work it in?

[Cal Leeming]

Patched, could someone please verify if this is suitable?

[James Bennett]

In [16808]:

Fixed #16293: Document a way to return dicts with column names from a DB cursor.

[James Bennett]

In [16809]:

[1.3.X] Fixed #16293: Document a way to return dicts with column names from a DB cursor. Backport of [16808] from trunk.