On Friday, May 17, 2013 4:23:39 AM UTC-4, Arnon Marcus wrote: > I have some more questions about using an alternative database for testing. > > What would happen to the schema-log file? > Wouldn't having the same model-code using 2 different databases, mess up > the log and brake automatic-migration capability? > I mean, you could turn migration off for when testing, but wouln't that > prevent the model from being able to actually create your tables? > Or does web2py manage different logs for each connection-url? > Same as how web2py would handle multiple databases in the same app in general -- see http://web2py.com/books/default/chapter/29/06#Migrations. By default, the *.table filenames are pre-pended with a hash of the db connection string (or you can manually name each .table file in the call to .define_table).
> And then there is the issue of having differences between schema > definitions using different databases, for example the way booleans are > implemented, or having missing features in the dal, like supporting > multy-column unique-constrains... I'm not even sure if sqlight supports > that at all... How would this approach handle such issues? > Obviously if you need to test database specific features, you'll need a copy of the specific database you want to test. Anthony -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
