« Return to Thread: Caching of describeTable

Re: Caching of describeTable

by GavinZend :: Rate this Message:

Reply to Author | View in Thread

Also, this general approach is time-proven.  For example, Qcodo is
relatively mature,
and has been used in "heavy-weight" applications.  However, I think some
will find the KISS ORM more suitable for "light-weight" applications.

http://framework.zend.com/wiki/x/bx0

I see the Qcodo style nicely complementing the KISS ORM proposal to
satisfy the 80/20.

Cheers,
Gavin

Darby Felton wrote:

> Another solution to the problem is using code generation, whereby
> classes are created upon introspection of the database structure. User
> classes extend the generated classes so that their code is not lost when
> the parent classes are regenerated.
>
> When the data schema changes, the developer simply reruns the code
> generator.
>
> This can be a reasonable solution for many situations, particularly for
> prototype and rapid application development.
>
> I know that Qcodo takes this approach: http://www.qcodo.com
>
> Best regards,
> Darby
>  

 « Return to Thread: Caching of describeTable