Forum OpenACS Development: Response to CONNECT BY solution

Collapse
Posted by Don Baccus on
At the time we made the decision they were undecided as to whether or not to adopt the SQL3 syntax.

To expand on Dan's list a bit, there's no way to enforce a unique key across a class and its subclasses, for instance the primary key, because each class and subclass has its own separate index (which you must remember to create by hand).  This is very bad.

Also, RI doesn't work with an inheritance tree at this time - the triggers will enforce RI integrity on the named class (i.e. relation/table) rather than the class and its subclasses.

As Dan said - lots of potential, but it's not really feature complete at this time.