This shows you the differences between two versions of the page.

Link to this comparison view

en:user_advanced:collection_database [2014/04/14 11:52] (current)
Line 1: Line 1:
 +====== Collection Database ======
 +The collection database dictates how data about your collection is stored. Greenstone comes with two database options: GDBM and JDBM. They are essentially the same; JDBM
 +is simply a Java implementation of GDBM. They are [[http://​en.wikipedia.org/​wiki/​Flat_file_database|flat file database]] engines. ​
 +You can select which of these to use in the [[en:​user:​browsing|Browsing Classifiers]] section of the [[en:​gli:​design_panel|Design panel]].
 +It is also possible to 
 +use a [[http://​en.wikipedia.org/​wiki/​Relational_model|relational database]] system, like [[http://​www.microsoft.com/​en-us/​sqlserver/​default.aspx|Microsoft SQL (MS-SQL)]]
 +to create your collection'​s database. Some notes on configuring Greenstone to achieve this are [[en:​developer:​mssql|here]].
 +===== GDBM =====
 +[[http://​www.gnu.org.ua/​software/​gdbm/​|GDBM (or GNU Database Manager)]] is a simple flat-file ​
 +database engine which Greenstone uses as the default database for new collections.
 +===== JDBM =====
 +[[https://​github.com/​jankotek/​JDBM3|JDBM (or Java Database Manager)]] is essentially a Java implementation of GDBM. Consider using this database engine combined with the Lucene indexer if you are wanting to create a pure Java run-time.
 +<TABAREA tabs="​Greenstone3,​Greenstone2">​
 +===== SQLite =====
 +SQLite is a simple relational database engine. It can be used in Greenstone to provide experimental advanced searching features that are not possible with the other database engines. To enable these features add "​sqlform"​ to the list of SearchTypes in the Format Features section of the Format tab.