MySQL profile_values definition doesn't match established integer length. [#12497]

Just working on a profile reporting idea and spotted that the following fields appear to have incorrect type definitions:
profile_values.fid = int(11)
profile_values.uid = int(11)

These both appear inconsistant with the rest of the database (that I have seen i.e. user tables) where they are defined as int(10). The profile_fields.fid is defined as int(10) also.

Comment	File	Size	Author
#1	05_dbprofile.patch	582 bytes	Morbus Iff
#1

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

File	Size
05_dbprofile.patch	582 bytes

Comment #2

Morbus Iff

they/them

CreditAttribution: Morbus Iff commented 16 March 2005 at 05:51

Title:

Database

» MySQL profile_values definition doesn't match established integer length.

Comment #3

Dries CreditAttribution: Dries commented 16 March 2005 at 21:25

Committed to HEAD. Thanks.

Comment #4

dors CreditAttribution: dors commented 18 March 2005 at 09:41

Shouldn't this also be honored in drupal/database/updates.inc?

Comment #5

Morbus Iff

they/them

CreditAttribution: Morbus Iff commented 18 March 2005 at 12:10

My feeling is that the "bug" is a matter of standardization -- NOT fixing it has no ill effect on anything whatsoever. If the consensus is that this SHOULD be in updates.inc, then I'll gen a patch for it.