FILE mode ignoring configuration for DB4O

Reported by Dave Leblanc:

Hi all, I'm having trouble handing in a configuration I've set up when
I'm using the FILE mode, eg:

       bindConstant().annotatedWith(Names.named(Db4Objects.PORT)).to
("0");
       bindConstant().annotatedWith(Db4Objects.class).to
("bigGame.db");

That part seems to get me using files ok, then if I want to provide a
different config:

       Configuration config = Db4o.newConfiguration();
       config.readOnly(true);

       // NOTE: we need to share some of the same config for client
and server (!)
       bind(Configuration.class).toInstance(config);

This doesn't work (I can write to the DB just fine, suggesting my
config changes aren't being applied).

Now, when I switch to LOCAL mode (which I'd prefer), this does accept
my config changes, but it fails in another weird way (which I should
probably describe in a separate email).

In summary, can we change the local file opening code to take a
configuration, eg:

       } else if (HostKind.FILE.equals(actualSettings.getHostKind()))
{
            return Db4o.openServer(configuration,
actualSettings.getDatabaseFileName(), actualSettings.getPort());
       }

Thanks,

 -Dave

Original issue reported on code.google.com by robbie.v...@gmail.com on 22 Feb 2009 at 6:29

wangscript / warp-persist

FILE mode ignoring configuration for DB4O #29