- Patch #12497 by Morbus: 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.
4.6.x
Dries Buytaert 2005-03-16 21:25:27 +00:00
parent 82565266b8
commit 9e32e74e66
1 changed files with 39 additions and 39 deletions

View File

@ -249,7 +249,7 @@ CREATE TABLE filter_formats (
name varchar(255) NOT NULL default '', name varchar(255) NOT NULL default '',
roles varchar(255) NOT NULL default '', roles varchar(255) NOT NULL default '',
cache tinyint(2) NOT NULL default '0', cache tinyint(2) NOT NULL default '0',
PRIMARY KEY format (format) PRIMARY KEY (format)
) TYPE=MyISAM; ) TYPE=MyISAM;
-- --
@ -459,8 +459,8 @@ CREATE TABLE profile_fields (
-- --
CREATE TABLE profile_values ( CREATE TABLE profile_values (
fid int(11) unsigned default '0', fid int(10) unsigned default '0',
uid int(11) unsigned default '0', uid int(10) unsigned default '0',
value text, value text,
KEY uid (uid), KEY uid (uid),
KEY fid (fid) KEY fid (fid)
@ -576,7 +576,7 @@ CREATE TABLE sessions (
timestamp int(11) NOT NULL default '0', timestamp int(11) NOT NULL default '0',
session longtext, session longtext,
KEY uid (uid), KEY uid (uid),
PRIMARY KEY sid (sid), PRIMARY KEY (sid),
KEY timestamp (timestamp) KEY timestamp (timestamp)
) TYPE=MyISAM; ) TYPE=MyISAM;