On 9/17/07, Thibaut Barrère <[EMAIL PROTECTED]> wrote: > > Word of warning, I am still seeing behavior with MySQL whereby indexes > > are not being retained in the temp table and thus will be lost when > > the temp table and renamed to the production table. You have been > > warned. > > Yep, my screens have detected this: the self-incrementing primary key > is always set to 0. > > Maybe I'll choose to use a notion of temporary database instead of > temporary table (either using the new MySQL rename database, or a > mysqldump). Another options would be to rename the tables to something > like "production_customers" at the end, and have the views pointing to > these (and the end-user would only see the views).
I'm going to work on fixing the temp table functionality in MySQL. V/r Anthony > > Just raw thoughts. > -- Cell: 321 473-4966 Current Location: Melbourne, FL _______________________________________________ Activewarehouse-discuss mailing list Activewarehouse-discuss@rubyforge.org http://rubyforge.org/mailman/listinfo/activewarehouse-discuss
