Opened 14 years ago
Closed 14 years ago
#14480 closed (invalid)
mysql and Django
| Reported by: | emmaxing | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 1.2 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi, the linux server of my company has mysql 1.2.1, which is too old for Django. However, the administrator didn't want to upgrade it. I have to install mysql 5.1.51 under my home directory. I did that successfully, but Django still complain about the older mysql. Do you know if there is a way to configure it so Django knows the path of the new mysql? Thanks.
Change History (2)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Hello, Trac is designed for filing bugs about Django itself, not for questions on how to use Django. For those you can use either the django-users mailing list, or the #django channel on irc.freenode.net.