uhm: are you sure that adding unique=True gets the created index also in the parent table ? I think that the unique is enforced only on creation and not in migration (but the requires=IS_IN_DB() gets added anyway). In any case, what are you observing? (in other words, post a model and a controller to reproduce the issue)
On Wednesday, December 5, 2012 12:08:03 PM UTC+1, Joe Barnhart wrote: > > This is probably old news, but I noticed this evening that altering a > table which is used as a "parent" by another does not cause its child table > to be altered. > > I have a table which I added a "unique=True" constraint on this evening > and its child table did not get the added constraint when web2py did its > migration. > > (I admit to being lazy and not searching to see if this has been reported > before. Google groups are pretty hard to search for something this > specific.) > > -- Joe B. > > --
