Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The db_update_field() function never should have been committed; it was my mistake to include it in the patch. It is very dangerous to have around because contrib authors will use it incorrectly (e.g. in a hook_update_N() function).
Core does not use it. Currently the only legitimate use for it is modules like CCK that dynamically modify tables but "like CCK" means "only CCK" and the function should just be part of CCK in D6.
Comment | File | Size | Author |
---|---|---|---|
#1 | db-update-field-173566-1.patch | 2.59 KB | bjaspan |
Comments
Comment #1
bjaspan CreditAttribution: bjaspan commentedPatch attached.
Comment #2
bjaspan CreditAttribution: bjaspan commentedI'll add that I marked this 'critical' because if we do not remove the function, contrib authors will use it incorrectly resulting in a situation that will be very difficult or impossible to recover from smoothly. Users will end up having to uninstall modules (drop tables) and reinstall to recover, losing data in the process. We really want to avoid that.
Comment #3
chx CreditAttribution: chx commentedRead drupal.org/node/150220 for more explanation.
Comment #4
Gábor HojtsyAgreed. I am glad this turned out before the beta. Committed.
Comment #5
(not verified) CreditAttribution: commented