Mike Sokolov wrote: Hi,
> So if you have, say, a development setup and a production > setup, they can share the same database names, but not the same > database ids. You can always get the id for a name using > xdmp:database() But my concern is that the name is not stable. You can change the name of one database, and in that case I want the config to still point to the same database. Of course, I always display the name instead of the ID in the user interface ;-) And by nature the config file is not aimed at being shared between instances, because it reflects a lot of other stuff installed and managed by the application. An export/import process for the whole or part of the "stuff" would make sense though, but then names would be used as part of that process, among many other things. Thanks for the thoughts Mike, it's been useful to decide that 1/ I want to keep using IDs ;-), 2/ I want to stop using the name I cache alongside the ID in the config (I rather want to always retrieve it from the ID when presenting to the user), and 3/ I want to keep the cached name in the config file, just for debugging purposes... Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
