You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Meenakshi Khatri <mk...@gmail.com> on 2010/09/03 16:25:38 UTC

naming conventions to name the tables for workspace and version

Hello everyone,

Could  you please tell me what is the most preffered naming convention to be
followed while naming workspace tables and version tables?

For my workspace: I am using:
<param name="schemaObjectPrefix" value="${wsp.name}_"/>

For my version: I am using:
<param name="schemaObjectPrefix" value="fs_ver_"/>

Also, I want to know if its a good idea to keep workspace and version tables
in one database or create 2 databases, one to handle workspace tables and
other to handle versioning.

Please let me know as soon as possible.

Thanks in advance,
Meenakshi

Re: naming conventions to name the tables for workspace and version

Posted by Meenakshi Khatri <mk...@gmail.com>.
Hello everyone,

Has anyone have experience in maintaining 2 seperates databases in
Postgres? One for Workspace and One for Versioning?

Is it beneficial to save both the details in one database?

Thanks and Regards,
Meenakshi

On Fri, Sep 3, 2010 at 4:25 PM, Meenakshi Khatri <mk...@gmail.com>wrote:

> Hello everyone,
>
> Could  you please tell me what is the most preffered naming convention to
> be followed while naming workspace tables and version tables?
>
> For my workspace: I am using:
> <param name="schemaObjectPrefix" value="${wsp.name}_"/>
>
> For my version: I am using:
> <param name="schemaObjectPrefix" value="fs_ver_"/>
>
> Also, I want to know if its a good idea to keep workspace and version
> tables in one database or create 2 databases, one to handle workspace tables
> and other to handle versioning.
>
> Please let me know as soon as possible.
>
> Thanks in advance,
> Meenakshi
>
>