Correction: I had the same problem, and don't have a good answer to why this occurs.
Could be something specifically a bug with Postgresql? The problem don't occur which sqlite. Besides, I always think the most annoying missing feature in web2py's DAL (and others orm's) is inability of use or adapt existent databases, without the boring redeclaring every field. In a really "enterprise" environment, most of databases already exists, so most of development is around it. I think in create a kind of wizard application to facilitate this task. It would use the following logic: 1.Define a connection *2. List all databases* *3*. List all tables of database. *4*. choose the *tables* to work *5*. list all fields of choosen tables *6*. auto-detect field relationships *7*. manually define field relationships *8*. check for necessary requirements for DAL and suggest solutions; the user choose the most appropriate solution and apply. (for me, solutions are only: create or rename the necessary field, especially id, would be could if DAL could accept declare a existent autoincrement field as id, while this real name is not. A possible solution is Postgresql is create a view redeclaring the name the field = my_id as id. ) *9*. DAL, as almost every orm, have a limited subset of fieldtypes, for compatibility for all databases. If a existent database have a non-standard DAL's fieldtype, is necessary define a solution how treat the data. So is necessary define a kind of conversion routine reading and writing for every non-standart fieldtype. The wizard would sugest some options or let the user define their own code. *10*. Finally, everything checked, generates the db model, including migrate=False. Something missing or any ideas? 2009/3/1 Alexandre Andrade <alexandrema...@gmail.com> > > > > > > 2009/3/1 annet <jmverm...@planet.nl> > > >> A couple of month ago I raised the following question: >> >> Every now and then simple changes to my model raise errors I do not >> understand. My PostgreSQL database contains example records for >> development purposes, so it is no big deal to drop and re-create some >> tables. But what if these errors occur after deployment on a >> production server. >> >> After initial deployment, when I continue developing my application, >> the database in my development environment will start to differ from >> the one on the production server. When I redeploy my application on >> the production server, the files that make up the model match my >> development database, but not my production database. How does web2py >> deal with these differences? >> >> >> Since the question wasn't answered I post it again, at the time of >> posting is was just me wondering about web2py's behaviour, now that I >> am nearing the point of deployment on a production server the answer >> to this question has become much more important. >> >> >> I wonder whether it is a good idea to put the database model in the >> init application and copy and paste it to the applications that make >> use of the model and set migrate to False? >> >> >> Best regards, >> >> Annet >> >> >> > > > -- > Atenciosamente > > -- > ========================= > Alexandre Andrade > Hipercenter.com > -- Atenciosamente -- ========================= Alexandre Andrade Hipercenter.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
