[BUGFIX] Use BLOB type column for ses_data in be_sessions table 14/51314/2
authorMorton Jonuschat <m.jonuschat@mojocode.de>
Sun, 15 Jan 2017 05:56:36 +0000 (21:56 -0800)
committerMarkus Klein <markus.klein@typo3.org>
Thu, 19 Jan 2017 01:35:17 +0000 (02:35 +0100)
The unified session handling for frontend and backend requires
identical SQL column types to properly escape the input data.
Using binary encoding for session data in combination with a TEXT
type field in the BE fails on PostgreSQL.

Change-Id: I3f3f379b43f873335207232e498f2e9e2c8b35e5
Resolves: #79324
Releases: master
Reviewed-on: https://review.typo3.org/51314
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Manuel Selbach <manuel_selbach@yahoo.de>
Tested-by: Manuel Selbach <manuel_selbach@yahoo.de>
Reviewed-by: Markus Klein <markus.klein@typo3.org>
Tested-by: Markus Klein <markus.klein@typo3.org>

index a3de277..18c2682 100644 (file)
@@ -42,7 +42,7 @@ CREATE TABLE be_sessions (
        ses_hashlock int(11) DEFAULT '0' NOT NULL,
        ses_userid int(11) unsigned DEFAULT '0' NOT NULL,
        ses_tstamp int(11) unsigned DEFAULT '0' NOT NULL,
-       ses_data longtext,
+       ses_data longblob,
        ses_backuserid int(11) NOT NULL default '0',
        PRIMARY KEY (ses_id,ses_name),
        KEY ses_tstamp (ses_tstamp)