Kenneth Gonsalves wrote: > > On 08-Aug-07, at 6:51 PM, Stephen Bunn wrote: > > use whatever permissions you are happy with. As long as the user > under which django accesses the database, can do everything django > requires to be done, it's fine. I dont think this is any different > from any other cgi application accessing a database. > therein lies the problem. What is 'everything' that Django requires to be done?
I know it obviously needs to be able to execute SELECT, UPDATE, and INSERT statements, but what about ALTER? SHOW? does it need to create views? create indexes? what about locking tables and creating temporary tables? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
