Received-SPF: none
 receiver=mail.tffenterprises.com; client-ip=207.154.33.2; envelope-from=john@techsuperpowers.com
From: John DeYoung <john@techsuperpowers.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: server wide vs. per-user
Message-Id: <05049384-F766-4D2A-9568-535D149E248E@techsuperpowers.com>
Date: Wed, 19 Mar 2014 12:36:39 -0400
To: CGPSA Discussion List <cgpsa-discuss@mail.tffenterprises.com>
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))

hi all -

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

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

sql_user_prefs =3D false

that would be the only change required to take us, suddenly, =
server-wide=85but then there=92s that voice that says that=92s 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=92re 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.
--=20
John DeYoung
Manager, Cloud Services
Tech Superpowers, Inc.