Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The extractor module currently stores and refers to the lookup vocabulary by its serial vid. This prevents you from consistently referring a particular vocabulary that has been exported using the Features module. This module should be patched to allow the option to use the non-serial "module name" to identify the vocabulary.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 836878_7.patch | 7.87 KB | alex_b |
| #3 | 875212_2.patch | 2.16 KB | Will White |
| #1 | 875212_1.patch | 2.16 KB | Will White |
Comments
Comment #1
Will White commentedPatch attached.
Comment #2
alex_b commenteddouble quotes (") in SQL statements don't conform to the standard, this would throw off PGSQL.
Have you done any performance testing on the
WHERE v.module = "%s"query? The number of selected items overall is high, while the number of vocabularies is usually very slow. I guess we are fine - unless the overall number of selected items requires an index no matter how low the number of items of the table we join to and filter by is (vocabulary)...Comment #3
Will White commentedNew patch fixes the double-quotes issue. Still needs a performance review.
Comment #4
alex_b commentedTo be released with alpha 4.
Comment #5
alex_b commentedAddressed performance issue by resolving the vid before using it in the query.
Comment #6
alex_b commentedCommitted, thank you.