On Thu, Apr 10, 2008 at 05:58:59PM -0700, Richard Klein scratched on the wall:
> My advice would be to try it and see. If table creation takes too long, > you can always remove the UNIQUE constraint, and then write a routine to > check the table for uniqueness after it's created. That "routine" could simply be creating an explicit unique index on the column after all the data is loaded. If the index can be created, you're good to go. This is still a slow process, but I know the creation of indexes on existing tables is one area the development team hopes to speed up. I'm not sure what the priority of that is, however. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "'People who live in bamboo houses should not throw pandas.' Jesus said that." - "The Ninja", www.AskANinja.com, "Special Delivery 10: Pop!Tech 2006" _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
