Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.See topic.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | nodewords_drop_backup_table-D6.patch | 568 bytes | hass |
Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.See topic.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | nodewords_drop_backup_table-D6.patch | 568 bytes | hass |
Comments
Comment #1
hass commentedAdditonally
db_query("DELETE FROM {variable} WHERE name LIKE 'nodewords%'");will delete external nodewords_* module variables, too. If someone on d.o writes a nodewords_foo module and have nodewords settings the uninstall will kill this variables, too and may make other modules unusable.nodewords_nodetype could be such a candidate... (currently no data loss, but possible)
Comment #2
hass commentedPatch attached for removal of backup table.
Comment #3
avpadernoThe table nodewords_10 has been intentionally left, and it contains the table has it was in the version 6.x-1.0 of the module.
The table will be removed from the update function for version 6.x-1.3.
Comment #4
hass commentedIf I'd like to get rid of all my nodewords stuff this table need to be removed. If you'd like to keep it for now and remove it in 7.x I'm fine to keep it. I'm only saying - if the module has intentionally *uninstalled* - everything in my database need to be cleaned out and there is no need to keep stale tables.
I may do not like to re-install nodewords any-time later...
Comment #5
avpadernoSee my previous comment; it was not my intention to keep it until the version for Drupal 7.
The code has been changed, and committed in CVS.
Comment #6
hass commentedI would suggest to keep the table for one release more (let's say half a year)... maybe there are more broken settings you need to recover. And with the kept table you are always able to recover with an update function later in 1.4 or so... otherwise if you are able to assure by 100000% that nothing is lost - remove it now.