[Marco van Herwaarden]

Originally Posted by KirbyDE

Hmm, it adds 1 Query to every Page being loaded,

Yes that is also why i wrote in my comment that we should discuss if testing if a product is active would be something that is really needed.

Keep in mind please that i also want this to be a disccusion, and if we all agree that this test is not worth the extra query, we could remove it easy.

Originally Posted by KirbyDE

As it requires an additional Query, what about the following:

A Table requirements with colums
scriptid
globaltemplates
actiontemplates
phrasetypes
specialtemplates
product
area

init.php would then query this table for the current scriptid/area, joined on products that are active.
Then merge the results with the current values and continue execution.

That would be an even more heavy query i guess.

Another alternative to the solution i have choosen here would be to load all this data from the XML-files (should be loaded on install of a product then) into a table, and then add this data serialized (hmm now i remember i wanted to add support for serialized datastore items, will do this tomorrow) to the datastore. This new record in the datastore shoudl always be queried when loading datastore items, and the load routine for the datastore could then dynamicly add those items to the datastore. But this would also mean another query (first query to retrieve this new record, then another to retrieve additional information, or retrieve all records from datastore, but only store the wanted ones into the $vbuleltin->datastore)