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.

CommentFileSizeAuthor
#1 db-update-field-173566-1.patch2.59 KBbjaspan
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bjaspan’s picture

Status: Active » Needs review
FileSize
2.59 KB

Patch attached.

bjaspan’s picture

I'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.

chx’s picture

Status: Needs review » Reviewed & tested by the community

Read drupal.org/node/150220 for more explanation.

Gábor Hojtsy’s picture

Status: Reviewed & tested by the community » Fixed

Agreed. I am glad this turned out before the beta. Committed.

Anonymous’s picture

Status: Fixed » Closed (fixed)