Just to add that since in the example below I do not use different schemas there is no guarantee the data are not corrupted, even though after running one test things look ok.
If I finally use Derby I will choose to go with the safe solution of using multiple schemas and a separate Derby DB for versioning. Giota -----Original Message----- From: Giota Karadimitriou [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 25, 2006 11:43 AM To: [email protected] Subject: RE: using one db for all filesystems and pms Something weird is definitely taking place there because I also had my share of failed efforts always having to do with cannot insert duplicate key sth.. I managed to create a single db only when using one persistence manager (SimpleDB..) and after hardcoding some of the paths. The repository.xml in that case looks like that: <Workspace name="${wsp.name}"> <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem"> <param name="path" value="${wsp.home}"/> </FileSystem> <PersistenceManager class="org.apache.jackrabbit.core.state.db.SimpleDbPersistenceManager"> <param name="driver" value="org.apache.derby.jdbc.EmbeddedDriver"/> <param name="url" value="jdbc:derby:${wsp.home}/db;create=true"/> . <param name="schema" value="derby"/> <param name="schemaObjectPrefix" value="default_"/> <param name="externalBLOBs" value="false"/> </PersistenceManager> . </Workspace> <Versioning rootPath="${rep.home}/versions"> <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem"> <param name="path" value="${rep.home}/versions"/> </FileSystem> <PersistenceManager class="org.apache.jackrabbit.core.state.db.SimpleDbPersistenceManager"> <param name="driver" value="org.apache.derby.jdbc.EmbeddedDriver"/> <param name="url" value="jdbc:derby:workspaces/db;create=true"/> . <param name="schema" value="derby"/> <param name="schemaObjectPrefix" value="default_"/> <param name="externalBLOBs" value="false"/> </PersistenceManager> </Versioning> If for some reason the first (bold) ${wsp.home} turns to workspaces I get the known exception for duplicate key. Giota -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Moseley Sent: Tuesday, January 24, 2006 7:06 PM To: [email protected] Subject: Re: using one db for all filesystems and pms On 1/24/06, Giota Karadimitriou <[EMAIL PROTECTED]> wrote: > For me at this point it would be best to use one db. I tried this with > embedded Derby and seems to work ok; I just wanted some extra opinion > just to verify I am on the right track: what does your repository.xml look like? i was never able to get it a one-db configuration to work with embedded derby.
