- What's new in Propel 2.0
- API Documentation
- Installing Propel
- Building a project
- Basic CRUD
- Logging And Debugging
- XML Schema Format
- Active Record Classes
- Active Query Classes
- Configuration Properties Reference
- Compatibility index
- Writing A Behavior
- User-Contributed Behaviors
- Working With Propel's Test Suite
- Additional SQL Files
- Advanced Column Types
- How to Use Namespaces
- Model Introspection At Runtime
- Multi-Component Data Model
- Object Copy
- Using Propel With MSSQL Server
- Using SQL Schemas
- Working With Existing Databases
- Working with Symfony2
- Working with Silex
Some features are not available through all PDO supported databases. You can see here a list of primary limitations.
At the moment we list only MySQL, SQLite and Postgres since only those are unit tested and fully supported.
1) As of version 3.6.19, SQLite supports foreign key constraints.
2) SQLite does not support named foreignKeys.
|Composite PK with one autoIncrement||Yes||Partial(2)||Yes|
1) SQLite does not support multiple columns with autoIncrement set to true.
2) SQLite does not support a composite PK where one of these is a autoIncrement. We support it anyways because we're setting primaryKey=false and create a unique constraint instead, which is at the end basically the same.
3) Only MySQL supports a concrete size at a
< 5.4.9 with PostgreSQL
If you're using < 5.4.9 and PostgreSQL you can't use
ATTR_EMULATE_PREPARES due to a bug in PHP's PDO that throws errors like:
column COLUMN is of type boolean but expression is of type integer
Update PHP to a newer version or disable