Thanks James, I thought about that, but how could I use that read-only user just in that Query.execute() function?
Cheers, Julien On Feb 3, 9:11 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Feb 3, 2008 4:00 AM, Julien <[EMAIL PROTECTED]> wrote: > > > What should I change to force the read-only access? > > Create a new database-level user, and grant that user SELECT but > nothing else. Then fill in those credentials in the settings file used > by the site. You can always set up a read/write "real" administrative > area for yourself with a different settings file and different > database credentials. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
