Date index for Dec 2002

Lukas Smith wrote:
> I think the key here is to have a nice API for every record type
> (however complex it may be) which seem to be the case with Achievo in
> most places.

It is. Achievo's backend ATK can manage almost any record type (come to 
think of it, I cannot name a single complex record type it wouldn't be 
able to deal with).

> The other thing that needs to happen is for one module to
> attach record sets to other record sets. This mostly boils down to the
> not everywhere available CASCADE on [UPGRADE|DELETE] feature set but
> could do much further.

This is already somewhat possible today. You can add relations between 
the different nodes (which represent tables). One of the things ATK can 
do is a cascade on delete of these relation records. The module API 
allows a developer to dynamically add a relation *in* another node (to 
your own node) so it is attached and the records could cascade on 
deletion of the "parent" record. Unfortunately it's not possible yet to 
do a cascade on update. This would be a nice feature though...

> Anyways there must be a way to register such dependencies and how
> them be resolved in a DB independent manner.

That's already possible (except for the CASCADE ON UPDATE part). So for 
the most part the Achievo backend is ready for a 1.0 release, I think.

Regards,

Peter