On 06/07/2006, at 4:56 AM, [EMAIL PROTECTED] wrote:
> > So does your database only have one user created and you specify > that in > the settings file or whenever you want to inspect the database by > hand? > > I'm under the impression that having a separate database user for the > web server and the developer is the Right Thing To Do(tm). > Unfortunately I don't find anything in the documentation, wiki, or > archives to support that idea. that's probably because it is outside of the scope of django itself ;-) what I usually do is create the schema via a SQL file with a 'admin' user, and then grant a restrictive access to the user I let django connect with. basically this protects me from 'DML' errors (ie dropping a table or an index) but not from deleting rows. If I were to be really 'anal' I would set up 2 separate settings files and make the updates go to a separate host with more access controls on it. but for the apps I'm writing now that isn't applicable. regards Ian > > Nate > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
