Data Stores
Zaapt is data store neutral meaning that any number of storage engines may be used with it. As long as the storage API implements and adheres to what Zaapt expects, it can be used with anything relatively sane.
Zaapt was designed and written to use PostgreSQL as it's backend storage, however it has been written in such a way that any back end store may be used. Of course, you probably want something that resembles a database but that's your choice.
The concept of models is used to describe how each content type works as well as what fields it needs to manage.
As an example, the API's are determined via the Zaapt::Model::* namespace
and the actual implementations are under the Zaapt::Store::*::* namespace.
For example, you may implement your models, such as:
Zaapt::Store::MySQL::*Zaapt::Store::SQLite::*Zaapt::Store::Firebird::*Zaapt::Store::SillyFlatFileFormat::*Zaapt::Store::WeirdTempMemoryStore::*
Let's take the News model. It's API is defined in Zaapt::Model::News,
it's PostgreSQL implementation is Zaapt::Store::Pg::News, it's MySQL
implementation is Zaapt::Store::MySQL::News and it's SQLite implementation
is Zaapt::Store::SQLite::News.
Soon there will be unit tests that should work with all storage backends.
Out of the box, Zaapt supports PostgreSQL since that could be called it's native store
(Ends)
Back to the Index.