Difference between revisions of "Other DBMS"
From OpenKM Documentation
| Line 1: | Line 1: | ||
{{TOCright}} __TOC__ | {{TOCright}} __TOC__ | ||
| − | OpenKM uses Lucene that means can be installed on major DBMS. By default OpenKM community tested DBMS are [[MySQL]] and [[PostgreSQL]]. In the OpenKM [http://www.openkm.com/en/overview/comparison-of-versions.html comparasion matrix] can see other DBMS tested at OpenKM professional version | + | OpenKM uses Lucene that means can be installed on major DBMS. By default OpenKM community tested DBMS are [[MySQL]] and [[PostgreSQL]]. In the OpenKM [http://www.openkm.com/en/overview/comparison-of-versions.html comparasion matrix] can see other DBMS tested and supported at OpenKM professional version. |
== Test in other DBMS == | == Test in other DBMS == | ||
Revision as of 12:14, 24 October 2012
Contents |
OpenKM uses Lucene that means can be installed on major DBMS. By default OpenKM community tested DBMS are MySQL and PostgreSQL. In the OpenKM comparasion matrix can see other DBMS tested and supported at OpenKM professional version.
Test in other DBMS
First you should know which is your hibernate dialect. For info about this take a look at Hibernate: SQL Dialects
To create the databases automatically configuring the hibernate.dialect and hibernate.hbm2ddl properties in OpenKM.cfg.
hibernate.dialect=org.hibernate.dialect.SomeDialect
hibernate.hbm2ddl=create
Once the tables are created, OpenKM will automatically change the hibernate.hbm2ddl property from create to none.
 |
Is possible depending your DBMS should be needed to make some minimal optimization in source code. Refer to Developer_Guide |
 |
This configuration property should be set before the database creation. Once the database has been initialized don't modify it because can damage your installation. If your OpenKM installation has been already configured with another database (default one is an embedded one called HSQL) you can't switch to another database simply changing this property. |
