I have the begging of something that may eventually get submitted, and looking
for guidance as I build it.
In the spirit of DRY, I have a nifty script that helps create the db defined in
settings.py
#!/usr/bin/env python
# mkdbuser.py
# prints the CREATE DATABASE and GRANT commands based on the local settings.py
import settings
SQL = """
DROP DATABASE IF EXISTS %(db)s;
CREATE DATABASE %(db)s;
GRANT ALL
ON %(db)s.*
TO %(user)s
IDENTIFIED BY '%(pw)s'
with grant option;
"""
print SQL % {
'db':settings.DATABASE_NAME,
'user':settings.DATABASE_USER,
'pw':settings.DATABASE_PASSWORD }
# end: mkdbuser.py
I pipe it into the client:
$ ./mkdbuser.py | mysql -u root -p
and presto! I have the db that syncdb wants.
I am thinking it would be nice if it was hung off of db/backends/mysql so that
it was driven by DATABASE_ENGINE and the various backends could spit out the
appropriate dialect.
I am also researching exactly what rights are needed by syncdb and runserver or
any production use so that what is spit out isn't quite so wide open. If
anyone
has already done this, I would rather not repeat it. :) however, if someone
wants me to anyway so we can compare notes to make sure we didn't mis anything,
thats fine too.
Carl K
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
