propelorm/Propel — pull request #174 by fzaninotto (2011-10-30 21:11:42+00:00)
Title: Fix archivable behavior when archive table is in another database.

There is a nasty bug causing the `archive()` method to use the wrong connection when called after `delete()`
(this is because we want to enclose the two operations in a transaction when they operate on the same database)
so we need to remove the connection parameter in case the user uses cross-databases archives.
A unit test for this case is quite heavy to set up (two more DBs to create), but I have tested it locally and it is OK.

More details in https://groups.google.com/d/msg/propel-users/c_3xYvxGpKw/grwMXrpjIlYJ