Re: database permissions
Kenneth Gonsalves wrote: > > > you have to divide the tasks into those that you want to do through > django and those that you want to do outside django - django needs > permissions to do the first set. I dont think one can be clearer than > that. > Understandable. But for somebody new to an ORM type model (like me) things might not be so clear. If I am writing a PHP or Perl application, I know exactly what permission it needs because I am constructing the SQL. With Django, it is building the SQL for me. Of course I could sit down and look at the source code and figure it out, but for somebody that is simply going through the tutorial to figure out if Django is for me, it would be nice to know what the minimal set of permissions are to get through the tutorial with it working. for my purposes I am just going to willy nilly give Django all permissions so I can test it out, but I still think it should be documented somewhere. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: database permissions
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 -~--~~~~--~~--~--~---
database permissions
Perhaps I am wrong, or just going about this the wrong way, but I have been looking the Django documentation and asking around in #django and nobody can (or do not want to) give me a straight answer and the minimum database permissions Django needs to operate. So I am assuming that everybody is just giving Django free rein over the database, which I think is a bad idea. Is there any documentation anywhere that describes setting up correct database permissions for use with Django. Thanks. Steve --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
