Fix odd behavior where calling $this->save() within after_create would create a whole new database entry instead of updating the current entry
The actual fix
Switched require to require_once to avoid "Cannot reload class" errors when multiple autoloaders are registered.
Minor change, getting around issue of multiple includes
Fixed set_class_name in the Relationship class to avoid fatal errors for "redeclared classes" in the autoloader when using namespaced models.
Merge pull request #293 from andyleap/master

Fixing require to require_once
Merge pull request #271 from brianmuse/master

Changed require in autoloader to require_once
Merge pull request #294 from onemightyroar/bug-fix-autoloader-reflection-class

Avoid "Cannot Redeclare Class" error in autoloader when using namespaced models by checking namespace first.
Merge pull request #267 from anther/after_create_fix

Fix for multiple db entries being created when calling `$this->save()` within an `after_create` callback method
added db config to travis.yml

Password for db users

postgres password change

enabled php memcache module

Removed PHP test suites (AllTests, AllValidationsTest)
Added test/helpers/config.php as bootstrap file
Merge pull request #285 from fetch/travis-db-config

Added db config for Travis (and removed extraneous references to `config.php`)
Now checking for an absolute namespace before appending to the existing namespace. To do this, a new Utils method called has_absolute_namespace was also created (for consistency with current Utils.php usage).
Adding a new model for deep namespace testing
New relationships for the namespace'd book model
Adding new tests to make sure that namespaced relationships work correctly
Using strpos, since its faster
Also, re-tabbing, since this project uses "hard" tabs
Merge pull request #296 from onemightyroar/bug-fix-namespaced-relationships

Error in `test_namespace_gets_stripped_from_table_name` (Travis Build 35)
Make sure that the primary key is stored in lowercase

Often, developers set the column names in different cases for the $primary_key static field in the Model. However, the object for the Model stores column names as lowercase (in $attributes). This causes confusion at times (for example, when checking if "$attributes[$pk]" is set while inserting a new record).

This small bit of code makes sure no matter what case the developer sets his primary key ("myPrimaryKey" or "myprimaryKey"), the key will always be stored in all lowercase ("myprimarykey").