says, for instance:

Create a new database

Now we will create another database from the xmark.xml document.

• Create the new database, named 'xmark'.

> CREATE DB xmark xmark.xml

• Set the new database xmark as the context:

> OPEN xmark

• Now you can easily execute queries on your new database:

> XQUERY //people/person/name

which to many would imply that a CREATE DB must be followed by an 'OPEN', or otherwise your use of the word 'now' doesn't make sense.

Ok - you want your users to guess what weird design decisions you made, and document them.  Unusual request.

On a more serious note, I'm wondering why?  In our application, we have a connection pool that maintains multiple sessions to the BaseX server for load balancing purposes. This is a commonly used technique I know you're familiar with from SQL databases.  With design decisions like yours that create per-session state as side-effects, you've just made this approach much more difficult to implement because each session now has to worry about how its activities might affect other sessions - even in applications where the current context is neither needed nor used.

My suggestion would be to rethink that decision and to not open the created database. If you must, provide a 'CREATE DB .... AND OPEN' command for use cases that need the db open after creation.

 - Godmar