Forum OpenACS Q&A: Response to What should be included in OACS 4.6

Collapse
Posted by Stephen . on
So your not saying that the oo-like features of the data model should be changed, but that some of the things we'd like to model do not need to be acs objects, like revisions for example?  How will we workflow revisions, permission them, or keep track of who created them?  What's the problem with the way it is now anyway, is it too slow?

I wouldn't be suprised if re-writing etp__get_title in Tcl made it slower, keeping in mind that plpgsql procedures have their query plans cached.  Most of the plpgsql in the toolkit doesn't even contain any procedural code, being a simple wrapper around one or more dml statements.  Sure, we don't want to do alot of processing on the db side, but I don't think there's many places where we do (and a couple of 'if' statements don't qualify, IMHO).