#5745: MySQL Collations/Charsets and Engines
------------------------------+---------------------------------------------
Reporter: Armin Ronacher | Owner: nobody
Status: new | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------+---------------------------------------------
Comment (by mtredinnick):
Before the comments really get out of hand...
This is probably worth doing in some limited form. I'd guess using the
existing DATABASE_OPTIONS setting is probably the most logical way,
similar to how MySQL's engine setting is supported now. It's not worth
adding it as an option to each model, since it's unlikely to vary between
models (and for those cases where it does, the initial SQL support can be
used). Two extra settings just for MySQL support is a little excessive,
too.
I'd want to rejig DATABASE_OPTIONS a little bit first, though, so that,
for example, we can differentiate between creation time options (engine,
collation, etc) and general connection options. That will require some
design work, but that's my thinking at the moment.
--
Ticket URL: <http://code.djangoproject.com/ticket/5745#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
