Hello Jack, I just migrate the tables forward. Generate a new one in my program and do a bulk insert from the old to the new, then drop the old one. At other times, I've just re-purposed the unused field.
C Tuesday, August 2, 2011, 7:03:52 AM, you wrote: JH> Hello all, JH> Is there a workaround for the lack of support for dropping JH> fields? I have an application and need to evolve the database JH> schema as features are added and removed. Leaving fields sitting JH> inside the database that are no longer used will lead to a schema JH> that is difficult to understand. Especially so when the field is JH> marked as NOT NULL. Years from now I will need to supply a value JH> for a field when inserting a row that has long ago ceased to be used. JH> Any ideas how I can remove unused fields from the database would be appreciated. JH> Regards, JH> Jack Hughes JH> _______________________________________________ JH> sqlite-users mailing list JH> sqlite-users@sqlite.org JH> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Best regards, Teg mailto:t...@djii.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
