PHP ActiveRecord is a great project. The only dreadful thing about it is that the code was written following a Ruby-like identifier naming convention - everything_goes_lowercase_underscorified.

Yet for modern PHP the canonical (and the most popular) naming style is camelCase.

I've corrected this misstep for myself and for everyone by restyling all the code of ActiveRecord from underscorified style to camel-cased one. The code is conceptually unchanged, all unit tests are being passed fine.

Camel case is now everywhere in ActiveRecord except database table and field names which must remain being written lowercase with underscores.

All methods, member variables and local variables are restyled. String identifiers like 'lesserThan' are camelized too as they should be.

Getter and setter methods of your models must also be written in camel-case. So if there is a field 'full_name' in a table, proper getter name will be getFullName().

Nothing, I think. The original documentation remains in force, except you need to read all identifiers with underscores as camel-cased.

It's possible that some minor bugs will pop with time, but they should be not critical as all unit tests are being passed correctly.

Canonical and consistent style of code in your projects. As the majority has chosen camel-case for PHP, you shouldn't go against or mix different naming conventions in your code. Your code should be beautiful.

New commits at kla/php-activerecord will be merged into this repo manually.

The original readme is below:

Version 1.0

by Kien La and Jacques Fuentes

http://www.phpactiverecord.org/

A brief summarization of what ActiveRecord is:

Active record is an approach to access data in a database. A database table or view is wrapped into a class, thus an object instance is tied to a single row in the table. After creation of an object, a new row is added to the table upon save. Any object loaded gets its information from the database; when an object is updated, the corresponding row in the table is also updated. The wrapper class implements accessor methods or properties for each column in the table or view.

More details can be found here.

This implementation is inspired and thus borrows heavily from Ruby on Rails' ActiveRecord. We have tried to maintain their conventions while deviating mainly because of convenience or necessity. Of course, there are some differences which will be obvious to the user if they are familiar with rails.

• PHP 5.3+
• PDO driver for your respective database

• MySQL
• SQLite
• PostgreSQL
• Oracle

• Finder methods
• Dynamic finder methods
• Writer methods
• Relationships
• Validations
• Callbacks
• Serializations (json/xml)
• Transactions
• Support for multiple adapters
• Miscellaneous options such as: aliased/protected/accessible attributes

Setup is very easy and straight-forward. There are essentially only three configuration points you must concern yourself with:

1. Setting the model auto_load directory.
2. Configuring your database connections.
3. Setting the database connection to use for your environment.

Example:

ActiveRecord\Config::initialize(function($cfg)
{
    $cfg->set_model_directory('/path/to/your/model_directory');
    $cfg->set_connections(
      array(
        'development' => 'mysql://username:password@localhost/development_database_name',
        'test' => 'mysql://username:password@localhost/test_database_name',
        'production' => 'mysql://username:password@localhost/production_database_name'
      )
    );
});

Alternatively (w/o the 5.3 closure):

$cfg = ActiveRecord\Config::instance();
$cfg->set_model_directory('/path/to/your/model_directory');
$cfg->set_connections(
  array(
    'development' => 'mysql://username:password@localhost/development_database_name',
    'test' => 'mysql://username:password@localhost/test_database_name',
    'production' => 'mysql://username:password@localhost/production_database_name'
  )
);

PHP ActiveRecord will default to use your development database. For testing or production, you simply set the default connection according to your current environment ('test' or 'production'):

ActiveRecord\Config::initialize(function($cfg) 
{
  $cfg->set_default_connection(your_environment);
});

Once you have configured these three settings you are done. ActiveRecord takes care of the rest for you. It does not require that you map your table schema to yaml/xml files. It will query the database for this information and cache it so that it does not make multiple calls to the database for a single schema.

These are your basic methods to find and retrieve records from your database. See the Finders section for more details.

$post = Post::find(1);
echo $post->title; # 'My first blog post!!'
echo $post->author_id; # 5

# also the same since it is the first record in the db
$post = Post::first();

# finding using dynamic finders
$post = Post::find_by_name('The Decider');
$post = Post::find_by_name_and_id('The Bridge Builder',100);
$post = Post::find_by_name_or_id('The Bridge Builder',100);

# finding using a conditions array
$posts = Post::find('all',array('conditions' => array('name=? or id > ?','The Bridge Builder',100)));

Here we create a new post by instantiating a new object and then invoking the save() method.

$post = new Post();
$post->title = 'My first blog post!!';
$post->author_id = 5;
$post->save();
# INSERT INTO `posts` (title,author_id) VALUES('My first blog post!!', 5)

To update you would just need to find a record first and then change one of its attributes. It keeps an array of attributes that are "dirty" (that have been modified) and so our sql will only update the fields modified.

$post = Post::find(1);
echo $post->title; # 'My first blog post!!'
$post->title = 'Some real title';
$post->save();
# UPDATE `posts` SET title='Some real title' WHERE id=1

$post->title = 'New real title';
$post->author_id = 1;
$post->save();
# UPDATE `posts` SET title='New real title', author_id=1 WHERE id=1

Deleting a record will not destroy the object. This means that it will call sql to delete the record in your database but you can still use the object if you need to.

$post = Post::find(1);
$post->delete();
# DELETE FROM `posts` WHERE id=1
echo $post->title; # 'New real title'