Demands a definition of global constants (for DatabaseTalker):
* DB_HOSTNAME
, DB_DATABASE
, DB_USERNAME
, DB_PASSWORD
-
v0.6.1
- Fixed issues while running tests
- Some fields were unreachable
- Some fields were non-existent
- Some
primary_key
fields weren't saving on_id
field - Changed method of verifying if certain property exists (in this case, is loaded)
- As before, only works after class is loaded with tables fields
- Since
property_exists
doesn't works with__isset
magic method,isset
will should behave the same asproperty_exists
- Another bugs the tests didn't catch may still appear, so beware!
- Fixed issues while running tests
-
v0.6.0
- Rewrote all docs looking for grammar issues, and also re-organization
- Changed the way EntityManager utilizes their "on demand fields columns population" as of the table definition
- Using magic methods
__get
and__set
- Using
ReflectorClass
- Using magic methods
-
v0.5.3
- Fixed incompatibility with PHP 5.3.8, in DatabaseTalker::hasArrayInMultiArray utility method, was passing function return as reference instead of variable.
-
v0.5.2
- Fixed problem where if the relation key where in the primary key (composite) the relation worked as if it had a pivot table.
-
v0.5.1
- Collection class now has unity tests for it's purpose (yes, everything is fine and dending now)
- Fixed some features with
sort
method
-
v0.5.0
- Created new class to deal with database querying and added new documentation
- New class to deal with database querying: DatabaseTalker!
- Database connection dependency is now ONLY on DatabaseTalker (can re-utilize connections as well)
-
v0.3.6
- Fixed some fields that still where possible to be referred as reserved words while querying
- Fixed possible issue where asserting an empty array (to clear the assertions) could cause some error.
- Add new function assertAdd, to assert new relations without destroying old ones.
-
v0.3.5
- New Features
- New method
whereRaw
for creating raw "where" queries - New method findByIdOrFail to maintain the last behaviour of throwing an error when not finding the entry
- New method
- Fixed issues:
- 'Time' fields weren't been parsed and saved correctly
- Added new tests:
- Verifying field types for dates/date-times/timestamps
- If they save correctly
- If they are parsed correctly
- for new method
whereRaw
- for new functionality of findById (returns null value instead of throwing an error)
- Verifying field types for dates/date-times/timestamps
- New Features
-
v0.2.2
- Fixed issue where if could get query errors when using column names of reserved words.
-
v0.2.1
- Fixed some issues
- Implemented tests for deleting methods
-
v0.2.0
- Added two new methods for deleting
- destroy($id required, $connection => default is NULL)
- Required $id, and can receive and outer PDO connection (for performance purposes)
- delete
- Deletes the instance from database (if it was saved)
- destroy($id required, $connection => default is NULL)
- Added two new methods for deleting
-
v0.1.0
-
v0.0.26
- Documentation fix
-
v0.0.25
- Added documentation for a starting guide.
-
v0.0.2:
- Customized table name (just define a table name on the protected attribute $table for the table name value)
- Customized primary key name ( just define a primary key name as string or composite primary key as an array of strings)
- Now supports composite primary keys (they must not be auto increment)
-
v0.0.1
- No documentation