hi all -

ages ago, when we started out with cgpsa, we chose to run per-user.  since then, among other improvements, we’ve switched to sql for the backend, which is great in all the ways you’d expect…but we’ve never gotten away from per-user filtering, and now it seems accuracy is all over the map as a result.  

looking through cgpsa.conf, i *think* what i’m seeing is that, if i were to set

sql_user_prefs = false

that would be the only change required to take us, suddenly, server-wide…but then there’s that voice that says that’s too easy, and i must be missing something.  that voice further specifies that, although the other options that talk about user prefs and user state all seem geared toward flat-file running, they’re probably still applicable to sql-run installs.

so.  am i, in fact, missing something?  or is it really that simple to switch from sql-based per-user filtering to sql-based server-wide filtering?

any insight greatly appreciated, naturally.

thanks,
-john.
--
John DeYoung
Manager, Cloud Services
Tech Superpowers, Inc.