[EMAIL PROTECTED] wrote:
> regarding how a developer would interact with any schema evolution
> implementation...would you prefer / see as more natural:
>
> 1) a commandline util only (via manage.py)
> 2) a web-based UI only (via the admin screens)
> 3) both
of course i would prefere to have both available.
but as the time is limited, I would prefere to see the efforts going
into a cmd-line utility.
so 1) (due to the limited time budget)
> (remember that we're likely talking about a multi-step upgrade process for
> more complicated modifications)
> if {2,3}, would you want the application to block (or redirect to a
> holding page) all incoming requests once it detects an update is needed?
wouldn't this be neccessary for a cmd-line update, too?
> aux question: my personal experience is that you should lock down alter
> table permissions away from the application's credentials. is this common
> in the django community?
I don't know about the django community, but personally, I would remove
all permissions which could become critical to application integrtiy.
Possibly the evolution tool should provide a mechnism to unlock them.
.
--
http://lazaridis.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" 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-developers
-~----------~----~----~----~------~----~------~--~---
