[ingo] Question about upgrading ingo

Patrick Boutilier boutilpj at ednet.ns.ca
Fri Feb 13 01:22:53 UTC 2009

Is there any reason the SQL statement to get the list of users can't be
changed to only include users that actually have any ingo rules? In my
case that drops the number of users that need to be parsed by
convert_prefs_to_sql.php from 112,106 to 16,207 . Am I making a wrong
assumption that only these users will have ingo rules that need upgrading?


'SELECT DISTINCT pref_uid FROM horde_prefs where pref_scope LIKE 'ingo''

 From docs/UPGRADING:

Upgrading Ingo From 1.1.x To 1.2

This is a non-exhaustive, quick explanation of what has changed between Ingo
version 1.1.x and 1.2.x.

SQL Backend

An SQL table has been added than can optionally be used as a storage backend
for the filter rules. Using this backend no longer limits the number and
of rules.

Execute the provided SQL script to add the table to your database, e.g.::

    mysql --user=root --password=<MySQL-root-password> <db name> <

You also have to execute the provided PHP script to migrate the existing
from the preferences backend to the new database table::

    php scripts/upgrades/convert_prefs_to_sql.php < filename

``filename`` is a file that contains a list of users, one username per line.
The username should be the same as how the preferences are stored in the
preferences backend (e.g. usernames may have to be in the form
user at example.com). You can create such a list with the following MySQL

    mysql --user=root --password=<MySQL-root-password>
--skip-column-names --batch --execute='SELECT DISTINCT pref_uid FROM
horde_prefs' <dbname>

More information about the ingo mailing list