Applications' db and jackrabbit db should 'em be the same?

[munguia <di...@rbxglobal.com>]

Hi,

I'm designing a new application that will use jackrabbit on the backend, I'm
planning to use the db persistence manager for jackrabbit and the
application will have it's own database as well. Both of them will be on
Postgres ... My question is, given the inner workings of the persistence
manager, is it recommended to have both the app's db and jcr's db on the
same schema (the pro that I'm seeing here for this is the simplicity of
backups) or is it better to have them on separated dbs/schemas?

Thanks.
Diego
-- 
View this message in context: http://www.nabble.com/Applications%27-db-and-jackrabbit-db-should-%27em-be-the-same--tp17539739p17539739.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Re: Applications' db and jackrabbit db should 'em be the same?

[Stefan Guggisberg <st...@day.com>]

hi diego

On Thu, May 29, 2008 at 6:23 PM, munguia <di...@rbxglobal.com> wrote:
>
> Hi,
>
> I'm designing a new application that will use jackrabbit on the backend, I'm
> planning to use the db persistence manager for jackrabbit and the
> application will have it's own database as well. Both of them will be on
> Postgres ... My question is, given the inner workings of the persistence
> manager, is it recommended to have both the app's db and jcr's db on the
> same schema (the pro that I'm seeing here for this is the simplicity of
> backups) or is it better to have them on separated dbs/schemas?

i don't see any problems with using a shared schema for your app and
jackrabbit data.

cheers
stefan

>
> Thanks.
> Diego
> --
> View this message in context: http://www.nabble.com/Applications%27-db-and-jackrabbit-db-should-%27em-be-the-same--tp17539739p17539739.html
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>

Re: Applications' db and jackrabbit db should 'em be the same?

[Alexander Klimetschek <ak...@day.com>]

Hi!

The persistence managers typically use a few tables for storing their
data. To separate them from other tables from other applications, you
can either create a separate schema/table space (or however that is
called in a specific db), which I would recommend, since it makes
adminstration generally easier.

Or, if you can only create tables you can use the schemaObjectPrefix
parameter in the db persistence manager configuration to separate the
tables from others. If the prefix is "jackrabbit_", you'll get
jackrabbit_nodes, jackrabbit_references and so on (depending on the
PM). Make sure you get the workspace name into the prefix - but this
should be clear when looking at the example repository xml files
and/or the PM documentation (javadocs of the PM class).

Regards,
Alex

-- 
Alexander Klimetschek
alexander.klimetschek@day.com