Thanks guys for the suggestions. However, what I'd like to have is that the site runs as per usual with a root user (with all priviledges), and that only one particular apps runs with a read-only user. Do I have to create a new connection object within my app code to override Django's, is it possible to ovveride the parameter via a setting file?
In PHP, since you create a connection object yourself, you can select which user (and also, which database, host, etc.) to execute a particular request. It would be great to make it easy in Django to allow that sort of flexibility, at least for custom made hard-coded SQL queries. On Feb 4, 8:15 pm, David Reynolds <[EMAIL PROTECTED]> wrote: > On 4 Feb 2008, at 1:59 am, Julien wrote: > > > I totally understand what you suggest, having a RO user at the > > database (in this case MySQL) level. > > But I am fairly new to Django and Python, and I am unsure how to > > implement that dual-setting option. > > In the devlopment server you can do > > ./manage.py runserver --settings=yoursite.readonlysettings # for the > display side of the site > > and > > ./manage.py runserver # for the admin side of the site > > When you deploy the site you can set up which settings file is used too. > > -- > David Reynolds > [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
