On Fri, Mar 13, 2009 at 6:02 AM, DenesL <denes1...@yahoo.ca> wrote: > > On Mar 12, 10:49 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > > On Thu, Mar 12, 2009 at 9:47 PM, DenesL <denes1...@yahoo.ca> wrote: > > > > > Actually we are currently using views in a way. > > > When a table is migrated the old fields remain in there but we can not > > > see them. > > > > I do not think so... here's an example of a recent migration I made > (resize > > a column): > > > > timestamp: 2009-03-09T12:19:48.093227 > > ALTER TABLE sample ADD name__tmp VARCHAR(64) UNIQUE; > > UPDATE sample SET name__tmp=name; > > ALTER TABLE sample DROP COLUMN name; > > ALTER TABLE sample ADD name VARCHAR(64) UNIQUE; > > UPDATE sample SET name=name__tmp; > > ALTER TABLE sample DROP COLUMN name__tmp; > > success! > > Which DB engine are you using?.
This was from Postgresql; you should expect the same from others. > > My statement seems to hold true for sqlite, the table still has the > old fields, I can execute select statements using them, it might be a > bug then. I will test with the latest trunk. I would not worry too much about sqlite for this right now - it is the least "like" the other db's wrt views. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
