On Wed, 16 Apr 2014 16:27:01 +0100
Simon Slavin <[email protected]> wrote:
> If you really want to do it in the TABLE definition, use the SQLite
> shell tool to '.dump' the table as a set of SQL commands, edit the
> dump file to add that constraint, then use the SQLite tool to '.read'
> the SQL command file.
Why not just create the new table, then
insert into S select * from R;
drop table R;
alter table S rename to R;
or similar?
If you're going to write out the data to a text file, wouldn't it be
faster to export the data to a delimited file and reload them
with .import? Why wrap them up in SQL?
--jkl
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
