The solution seems to be simply to make it a "standalone" database.
Can anyone see any problems with that approach? Do we need the environment for anything?
Like Neal, I'm not entirely sure I understand your use of "standalone." IIRC, you're talking about the DB_ENV "environment" access to the database.
I do not think we currently use the Berkeley environment support for anything much. IIRC, it's for client-server operation. But then again, it looks like you want DB_ENV for the Berkeley-level locking and transaction support, which we may want.
-Geoff
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
