Feature Request

[TheDucc]

I am trying to place production safeguards on a pouch to couch sync. The use case I imagine is that a couchDB was destroyed; but the couch users still exists. When using your code under these circumstances I get an error on trying to create a user that already exists. This make sense, of course.

I have already written code that checks for the existing user doc and the db name on the couch remote server. So passing additional GET variables to create both or just the DB would be simple from my perspective.

I am not worried about a missing user doc attached an existing DB; because creating a new user/DB pair is fine in this use case.

Can you offer me any support on this?

dmd

[ronycohen]

Hello @TheDucc did you find your answers ?

[TheDucc]

In short: Yes. But the answer was non ideal.

I was unable to allocate anymore 'struggle' time to the project that created this forum comment. And did not have time to alter this project's code to add the new functionality. But suspect that I will need to come back to is some day, since I rely heavily on couch in most of my new projects.

And therefore I still think that separating the user and doc collection creation would be useful.