phpalchemy/propel-service-provider

Propel integration for PhpAlchemy.

PropelServiceProvider

The PropelServiceProvider provides integration with Propel2., _(*1)

Parameters

• propel.path (optional): The path in which Propel.php will be found. Usually, for PEAR installation, it is propel while for Git installation it is vendor/propel/runtime/lib. Default is /full/project/path/vendor/propel/propel1/runtime/lib., _(*2)

• propel.config_file (optional): The name of Propel configuration file with full path. Default is /full/project/path/build/conf/projectname-conf.php, _(*3)

• propel.model_path (optional): Path to where model classes are located. Default is /full/project/path/build/classes, _(*4)

It's strongly recommanded to use absolute paths for previous options., _(*5)

Services

No service is provided., _(*6)

Propel configures and manages itself by using static methods, so no service is registered into Application. Actually, the PropelServiceProvider class initializes Propel in a more "PhpAlchemy-ian" way., _(*7)

Registering

Make sure you place a copy of Propel in vendor/propel or install it through PEAR, or Composer., _(*8)

For more informations consult the Propel documentation:, _(*9)

``` php <?php, <sub>(*10)</sub>

$app['propel.config_file'] = DIR.'/path/to/myproject-conf.php'; $app['propel.model_path'] = DIR.'/path/to/model/classes'; $app->register(new Propel\Silex\PropelServiceProvider());, <sub>(*11)</sub>

Alternatively, if you 've installed Propel by Git in `vendor/propel` and
you built your model with default Propel generator options:

``` php
<?php

$app->register(new Propel\Silex\PropelServiceProvider());

We can consider "default" Propel generator options:, <sub>(*12)</sub>

• Put build.properties and schema.xml files into the main directory project, usually where file index.php is located., <sub>(*13)</sub>

• In build.properties file, define only propel.database, propel.project and propel.namespace.autopackage properties., <sub>(*14)</sub>

Usage

You'll have to build the model by yourself. According to Propel documentation, you'll need three files:, <sub>(*15)</sub>

• schema.xml which contains your database schema;, <sub>(*16)</sub>

• build.properties more information below;, <sub>(*17)</sub>

• runtime-conf.xml which contains the database configuration., <sub>(*18)</sub>

Use the propel-gen script to create all files (SQL, configuration, Model classes)., <sub>(*19)</sub>

By default, the PropelServiceProvider relies on the PhpAlchemy autoloader you have to configure to load model classes. Of course, the Silex autoloader needs the model to be built with namespaces, so be sure to set this property into the build.properties file:, <sub>(*20)</sub>

``` yaml propel.namespace.autopackage = true, <sub>(*21)</sub>

The recommended configuration for your build.properties file is:, <sub>(*22)</sub>

propel.project = , <sub>(*23)</sub>

propel.namespace.autoPackage = true propel.packageObjectModel = true, <sub>(*24)</sub>

Enable full use of the DateTime class.

Setting this to true means that getter methods for date/time/timestamp

columns will return a DateTime object when the default format is empty.

propel.useDateTimeClass = true, <sub>(*25)</sub>

Specify a custom DateTime subclass that you wish to have Propel use

for temporal values.

propel.dateTimeClass = DateTime, <sub>(*26)</sub>

These are the default formats that will be used when fetching values from

temporal columns in Propel. You can always specify these when calling the

methods directly, but for methods like getByName() it is nice to change

the defaults.

To have these methods return DateTime objects instead, you should set these

to empty values

propel.defaultTimeStampFormat = propel.defaultTimeFormat = propel.defaultDateFormat = ```, <sub>(*27)</sub>

If you plan to build your model without using namespaces, you need to force Propel to use its internal autoloader. Do this by setting the option propel.internal_autoload to true., <sub>(*28)</sub>

For more information, consult the Propel documentation., <sub>(*29)</sub>