The mailing list for listmasters using Sympa

["Mail administrator, Otto Makela" <address@concealed>]

Question for someone who understands the underlying database structure:

We've been automating some lists that used to have manually subscribed
users to now include them via LDAP lookups. We've ended up with lists with
users that were subscribed but are now also included from the data source.
We'd like to get rid of such duplicate subscriptions (so that users get
nicely removed from the list once the database changes), but doing this
via the GUI would be major chore.

Many Sympa versions ago, it was possible to directly change the underlying
SQL database to change user status for those that were both "subscribed"
and "included" with the command:

UPDATE subscriber_table SET subscribed_subscriber=0 WHERE  
subscribed_subscriber=1 AND included_subscriber=1;

This still seems to work, afterwards these users show up as only being
included from the data source. Is this currently an acceptable one-time
way to resolve this kind of duplicates, or is there some major caveat?

--
address@concealed (Mail Administrator, Otto J. Makela)