Project

General

Profile

Actions
Copy link

Bug #16774

closed

content field of fe_session_data should use mediumtext instead of mediumblob

Added by Michiel Roos almost 18 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Christian Kuhn
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2006-12-08
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.0
PHP Version:
4
Tags:
Complexity:
Is Regression:
Sprint Focus:

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 ;-).

#
  1. 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:

#
  1. 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)

Files

Download all files
ext_tables.sql.diff (551 Bytes) ext_tables.sql.diff Administrator Admin, 2006-12-11 09:42
tables.sql.diff (1.23 KB) tables.sql.diff Administrator Admin, 2006-12-11 09:46
Actions
Copy link

Also available in: Atom PDF