Comment 2 for bug 707741

It was r12215. The problematic code is now wrapped in SlaveDatabasePolicy (not SlaveOnlyDatabasePolicy, so it is allowed to use the master when required, so it should work).

Now, the librarian upload protocol checks that the server and client are using the same DB. But FileUploadClient.addFile uses the old SQLObject-compatible cursor() method to determine the database name, which uses the default store, which in this case is the slave, when file creation should obvious use the master.

Perhaps addFile should explicitly use the master?