The Configuration File (Part 2 - Database modes)

In a previous post I wrote about the modes section in the Tlalokes framework configuration's file. But the topic about the database mode was pending.

Tlalokes uses the Propel as ORM in order to work with databases in the same way you work with other classes and objects in PHP. Propel uses an XML schema to define the object-database relation. But it requires write this XML and then run a Phing command provided at the Propel generator in order to build objects, database tables, etc.

Tlalokes provides a simplified way to use Propel, instead of running Phing "tasks" manually throw the CLI Tlalokes runs them for you, the only thing you have to do is to specify the database mode, and then, before your application loads Propel runs its "tasks" and that's all.

Tlalokes simplifies the way to define the relation between tables and mapping objects, instead of using and XML schema it uses annotated classes named Definition-Objects.



The database mode provides you the following options:

build-conf. Generates the Propel's configuration files.

build-tables. Generates the tables at the database based in Definition-Objects. Previously you must setup the DSN section in the configuration file.

build-all. Generates the database tables, and the ORM objects.

build-from-db. Generates the ORM objects from existent database.

build-om. Generates only the ORM objects from Definition-Objects.

alter-tables. Actually in development, regenerates and execute alteration SQL files in order to modify your database tables according to your Definition-Objects. Right now just works with PostgreSQL.

production. This mode skips any Propel task.