Recent changes to feature-requests

findAll should handle other operators

2008-06-28T17:21:08Z

The findAll method should accept parameters which indicate other operators besides equality (and LIKE). For example, instead of just passing in 'field1'=>'value1', one could also pass in 'field1'=>array('operator'=>'!=', 'value'=>'value1')

Better DB field attribute definitions

2008-06-16T16:00:46Z

It would be better if the attributes of a database field/property could be specified in annotation style comment on the field versus in static fields that can't be used with an instance of the class.

Documentation & example code

2008-06-13T14:13:01Z

We would like to have full documentation and example code

Lazy loading of entity relationships

2008-06-13T14:11:14Z

*** This request depends on request 1993017 ***

Allow entity to specify whether its relationships should be loaded immediately upon retrieval or only when requested.

Implement entity relationships

2008-06-13T14:04:13Z

Currently the DBEntity class only handles flat fields. We would like to implement support for entity relationships. This would also involve the retrievel of those relationships and the parsing of the Entity which would contain those definitions.

Abstract Logger module

2008-06-13T14:01:22Z

Currently DBEntity will always use the homegrown Logger object for all logged events. We should abstract out the Logger module so that any logger could be used which follows some specific format. This involves changing DBEntity to accept a Logger object somehow.

Abstract DB connection module

2008-06-13T13:55:39Z

Currently DBEntity will always use the homegrown DBConn object for connection to MySQL. We should abstract out the connection module so that any connection module could be used which follows some specific format.

This may involve multiple tasks:
- Create abstract DBConn class
- Implement DBConn with MySQL specific class (and any others)
- Change DBEntity to accept a DBConn object somehow