#5203: Performance improvement for sqlite3 database flush
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Database wrapper
Version: SVN | Resolution:
Keywords: sqlite performance | Stage: Design decision
needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------+---------------------------------------
Comment (by [EMAIL PROTECTED]):
>>When you say "changing the PRAGMA settings may corrupt the database"
does this mean "may corrupt the
>>entire database file" or "may corrupt the information in the table, but
that's ok since we're
>>deleting it anyway"?
The whole database file can be corrupted, I believe.
>>For flushing the database, the risk doesn't look that bad to me.
Right. Especially since the flushing will be done by a system
administrator and when normal usage of the application is suspended.
>>Although perhaps the original poster can explain why this is a
particularly relevant optimisation.
In absolute terms the savings are probably small.
For "real" database engines other than sqlite the tuning of the database
is to be done outside of the django application by a database
administrator.
When using django with sqlite the django app is much more directly
responsible for the database. And one might expect django to capture the
best practices in this area...
My 2 cents: I thought a ticket was relevant since it does capture such a
good and common practice.
--
Ticket URL: <http://code.djangoproject.com/ticket/5203#comment:4>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
