Forum OpenACS Q&A: Re: Server recommendation for 20,000 users in dotLRN?

Collapse
Posted by Don Baccus on
Actually I wasn't talking about using Oracle's materialized view feature but rather using triggers in PG and Oracle to maintain a materialized version of the person_member_map.  Sorry for the jargon confusion.

This will only change when people are added or deleted to groups (say, a class in dotLRN or the membership group for the site at large).

There's also a view specific to PG in the permissions system that we're materializing via triggers and that one only changes when new privileges are added, typically when a new package is installed.

I've done some reading on Oracle's materialized views and they seem all bound up with replication and distributed databases and less oriented towards something simple like this.  The more I read about them the more the words "complexity" and "high overhead" came to mind.

Since we know the relationships between various tables and the views in question we can write reasonably efficient triggers to maintain the tables.