Thanks - I already do nightly backups of data and code (been stung too many times before).
I want to use Web2p as you say, but I've had problems in the past. 2-3 times, no matter what I've tried, I couldn't edit the DB.py file and avoid crashes. Ended up deleting tables, massaging data with MS Access, recreataing with difference nemae and reocdign etc. etc. Also, I can't point the app at an empty MySQL database and let it build the tables. Have to rely on a backup to recreate empty tables first. I haven't kept any evidence, but I will post it here next time (if it happens again). Have you had problems with MySQL users before??? Really enjoying using Web2py - I'm building a test support/management tool to support our business services. Very happy with the development progress and just a few niggles - this is one of them. Working through others... Thanks again. On Jul 21, 11:07 am, mdipierro <[email protected]> wrote: > It is better to always use web2py but remember to use (default) > migrate=True every time you edit the db. > You may also want to keep a backup of your database/*.tables > > On Jul 21, 4:54 am, Paul Gerrard <[email protected]> wrote: > > > > > An updqate. > > > I read the manual 6.4 on Migrations. I've added a migrate='tablename' > > aramter to the table definition call. It seems to work. > > > So I guess I've disconnected the table definition from the Web2py > > table history. So far so good. > > > So I have a more general point. > > > "Is it 'better' to manage database designs using the Web2py model or > > better to manage the database using the DB utilities and keep the > > model in sync?" I understand the web2py model route ought to be > > better, but this is the second time I've lots hours messing around > > with out of sync database and models.- Hide quoted text - > > - Show quoted text -
