#16774content field of fe_session_data should use mediumtext instead of mediumblob
Description
As far as I can tell, only string data is stored in the content field of the fe_session_data table. I don’t understand why mediumblob was chosen as data type.
Mediumtext should do just fine for text.
Problems arise when installing on postgres.
The mediumblob gets cast to a bytea.
This gives me problems when selecting from the content field from within xforms ;-).
#- Table structure for table ‘fe_session_data’
#
CREATE TABLE fe_session_data (
hash varchar(32) DEFAULT ‘’ NOT NULL,
content mediumblob NOT NULL,
tstamp int(11) unsigned DEFAULT ‘0’ NOT NULL,
PRIMARY KEY (hash)
);
Should read:
#- Table structure for table ‘fe_session_data’
#
CREATE TABLE fe_session_data (
hash varchar(32) DEFAULT ‘’ NOT NULL,
content mediumtext NOT NULL,
tstamp int(11) unsigned DEFAULT ‘0’ NOT NULL,
PRIMARY KEY (hash)
);
(issue imported from #M4628)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.