Forum OpenACS Development: Re: Saving List Views (add to core?)

Collapse
Posted by Dave Bauer on
Malte, maybe there is a way to save each in a seperate column , but it seems like overkill since the session level property is saved as a list (of lists of lists?) that needs to be parsed anyway. Maybe there should be seperate session properties too. Anyway thats an implementation level detail we can work out as we go.

My point is that acs-templating does not seem to rely on the content repository, although they are both part of core, in general there isn't any database code in the templating package.

Collapse
Posted by Malte Sussdorff on
Ah, okay, but you could rely easily and you do not have to have a SQL directory if you call content::type::new (unless I misunderstood the implementation, but it should create the extension table for you, shouldn't it). Though now we are getting into the area of "is it a best practice to create the tables in the SQL statement instead of only calling the TCL methods".

I agree we need to do some parsing, but we have a database, so why not use it? Parsing should be left to the situations where we do not know which columns we have, but in this scenario we know at least some of them.

Collapse
Posted by Tom Jackson on
Dave,

What does the data look like that you are storing? This sounds like a state store/restore operation.