Selecting database in a view adds it to the query

[azul]

The database method on views allows specifying the database to query from.

  User.by_login.database(User.tmp_database).key("bla").first

However the database parameter gets added to the query so it's also present in the url. So the couch logs for this query for me show:

GET /tmp_users/_design/User/_view/by_login?database=http%3A%2F%2Flocalhost%3A5984%2Ftmp_users&key=%22bla%22&limit=1&include_docs=true&reduce=false 200

I would expect the query to not contain the database:

GET /tmp_users/_design/User/_view/by_login?key=%22bla%22&limit=1&include_docs=true&reduce=false 200

The database parameter clutters the query and also leaks credentials in the couch logs.

[azul]

I've looked into implementing a fix for this a bit. I see two options...
The hacky one... remove the database parameter from the query. This would have the ugly sideeffect of removing the parameter even if it was explicitly set.
The more correct one (?)... use something else than the query to store the database in. This is kind of complicated because of the nice way queries are build by chaining calls and creating new instances of the view. The initializer already has 4 parameters. The best way would probably be to fetch it from the parent like we currently do with name.