Ah, this explains the error I got when I originally defined a boolean column with "not null" and later deleted it. I found I could no longer insert records into the table because the "dropped" column had no value and thus was always trying to insert a NULL. I recovered by dropping the whole database and recreating it (since I am not in production yet).
A more surgical approach would be needed if I had data I cared about... <g> On Jan 25, 10:56 am, mdipierro <[email protected]> wrote: > It is not that. > SQLite does not actually enforces column time and therefore does not > support DROP COLUMN. > This means are never really dropped, are only just ignored. > > Massimo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
