In exporter.py, dump_modules() method, it builds "pkgerrata2module:<pkg_id>:<errata_id>" entries that are supposed to contain a set of module_ids or module_stream_ids.
What it currently puts in the set is the module_stream_id from the pkg_errata table. The pkg_errata table has a unique constraint on (pkg_id, errata_id), so there can never be more than one value placed in the set with key "pkgerrata2module:<pkg_id>:<errata_id>".
So either this db query was intended to join pkg_errata to module_stream on module_stream_id in order to get the module_id's to put in the set, or there is no need for a set to hold the value keyed on "pkgerrata2module:<pkg_id>:<errata_id>".
In exporter.py, dump_modules() method, it builds "pkgerrata2module:<pkg_id>:<errata_id>" entries that are supposed to contain a set of module_ids or module_stream_ids.
What it currently puts in the set is the module_stream_id from the pkg_errata table. The pkg_errata table has a unique constraint on (pkg_id, errata_id), so there can never be more than one value placed in the set with key "pkgerrata2module:<pkg_id>:<errata_id>".
So either this db query was intended to join pkg_errata to module_stream on module_stream_id in order to get the module_id's to put in the set, or there is no need for a set to hold the value keyed on "pkgerrata2module:<pkg_id>:<errata_id>".