An extra safety feature is always welcome, so I'm not arguing against that idea, I'm simply mentioning another point.
I mean, whatever security system you use, you will need a safeguard which works when you copy your files over. e.g. You set all your tables to 'insecure' on your dev system, and to 'secure' on the production machine. Now what happens when you upload your app? On Feb 25, 12:24 am, Carlos <[email protected]> wrote: > Hi villas, > > Thanks for your recommendation. > > Ideally I would really like web2py to take care of all db migrations, but > only with the proposed safety flag (or something similar) at the field > level, i.e. *explicit* permission to delete or alter each field. > > Or maybe have a separate (but integrated) migration tool that takes care of > these migrations that involve data loss?. > > Comments?. > > Thanks again, > > Carlos
