- 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
parent
82565266b8
commit
9e32e74e66
|
@ -249,7 +249,7 @@ CREATE TABLE filter_formats (
|
|||
name varchar(255) NOT NULL default '',
|
||||
roles varchar(255) NOT NULL default '',
|
||||
cache tinyint(2) NOT NULL default '0',
|
||||
PRIMARY KEY format (format)
|
||||
PRIMARY KEY (format)
|
||||
) TYPE=MyISAM;
|
||||
|
||||
--
|
||||
|
@ -459,8 +459,8 @@ CREATE TABLE profile_fields (
|
|||
--
|
||||
|
||||
CREATE TABLE profile_values (
|
||||
fid int(11) unsigned default '0',
|
||||
uid int(11) unsigned default '0',
|
||||
fid int(10) unsigned default '0',
|
||||
uid int(10) unsigned default '0',
|
||||
value text,
|
||||
KEY uid (uid),
|
||||
KEY fid (fid)
|
||||
|
@ -576,7 +576,7 @@ CREATE TABLE sessions (
|
|||
timestamp int(11) NOT NULL default '0',
|
||||
session longtext,
|
||||
KEY uid (uid),
|
||||
PRIMARY KEY sid (sid),
|
||||
PRIMARY KEY (sid),
|
||||
KEY timestamp (timestamp)
|
||||
) TYPE=MyISAM;
|
||||
|
||||
|
|
Loading…
Reference in New Issue