#9206: Improve documentation on raw SQL queries
-----------------------------------------------------------------------+----
Reporter: Richard Davies <[email protected]> |
Owner: nobody
Status: closed |
Milestone: 1.1
Component: Documentation |
Version: SVN
Resolution: fixed |
Keywords:
Stage: Accepted |
Has_patch: 1
Needs_docs: 0 |
Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------------------------+----
Changes (by russellm):
* status: reopened => closed
* resolution: => fixed
Comment:
Richard: Thanks, but I left that bit out deliberately - I might be missing
the point, but I didn't really see what that section was adding to the
discussion. The fact that django uses a pseudo-autocommit mode is covered
earlier, and isn't Postgres specific. The operation of the database-native
autocommit mode is discussed in the docs for the Postgres binding (which
is linked to). To me, the 'missing' paragraph only served to confuse the
issue of what autocommit meant. This comes back to Malcolm's comment about
auto-commit confusion.
I'm fully willing to admit that more documentation may be required - It
just isn't obvious to me what is missing (or how the paragraph I omitted
could be turned into the missing piece). If you feel there is some vital
information that needs to be included, feel free to work up another draft
for that paragraph and we'll take a look at it.
--
Ticket URL: <http://code.djangoproject.com/ticket/9206#comment:5>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
