#10936: Detailed instructions for getting Django and MySQL and MySQLdb working
on
various OS X versions
---------------------------------------------+------------------------------
Reporter: simon | Owner: nobody
Status: new | Milestone:
Component: Documentation | Version: SVN
Resolution: | Keywords: mysqldb
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by mtredinnick):
Both of the assertions in comment:5 aren't correct. MySQL is tested at
least as much as PostgreSQL, arguably has more code in Django to support
it and is quite possibly even used more in terms of raw numbers, since
it's the default with a bunch of hosting accounts. Also, developing
against a database other than SQLite3 is often a good idea. Even necessary
if you're using some of the database-specific features, such as postgis or
text-field searching (MySQL) or stored procedures (vary per database),
etc.
I feel this whole ticket is probably a bit out-of-scope, since being a
sysadmin for your box isn't really a goal of Django. Some pointers to
links to help people do that setup or, as noted elsewhere, a wiki page
maintained by people who actually do this and need it would probably be
more efficient and accurate.
--
Ticket URL: <http://code.djangoproject.com/ticket/10936#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
