-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Added a note about session data size in PdoSessionHandler #5516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,7 @@ How to Use PdoSessionHandler to Store Sessions in the Database | |
The default Symfony session storage writes the session information to files. | ||
Most medium to large websites use a database to store the session values | ||
instead of files, because databases are easier to use and scale in a | ||
multi webserver environment. | ||
multiple web server environment. | ||
|
||
Symfony has a built-in solution for database session storage called | ||
:class:`Symfony\\Component\\HttpFoundation\\Session\\Storage\\Handler\\PdoSessionHandler`. | ||
|
@@ -172,15 +172,18 @@ of your project's data, you can use the connection settings from the | |
'%database_password%', | ||
)); | ||
|
||
Example SQL Statements | ||
---------------------- | ||
.. example-sql-statements:: | ||
|
||
Preparing the Database to Store Sessions | ||
---------------------------------------- | ||
|
||
Before storing sessions in the database, you must create the table that stores | ||
the information. The following sections contain some examples of the SQL statements | ||
you may use for your specific database engine. | ||
|
||
MySQL | ||
~~~~~ | ||
|
||
The SQL statement for creating the needed database table might look like the | ||
following (MySQL): | ||
|
||
.. code-block:: sql | ||
|
||
CREATE TABLE `session` ( | ||
|
@@ -193,8 +196,6 @@ following (MySQL): | |
PostgreSQL | ||
~~~~~~~~~~ | ||
|
||
For PostgreSQL, the statement should look like this: | ||
|
||
.. code-block:: sql | ||
|
||
CREATE TABLE session ( | ||
|
@@ -207,8 +208,6 @@ For PostgreSQL, the statement should look like this: | |
Microsoft SQL Server | ||
~~~~~~~~~~~~~~~~~~~~ | ||
|
||
For MSSQL, the statement might look like the following: | ||
|
||
.. code-block:: sql | ||
|
||
CREATE TABLE [dbo].[session]( | ||
|
@@ -225,3 +224,16 @@ For MSSQL, the statement might look like the following: | |
ALLOW_PAGE_LOCKS = ON | ||
) ON [PRIMARY] | ||
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY] | ||
|
||
.. note:: | ||
|
||
If the session data doesn't fit in the data column, it might get truncated | ||
by the database engine. To make matters worse, when the session data gets | ||
corrupted, PHP ignores the data without giving a warning. | ||
|
||
If the application stores large amounts of session data, this problem can | ||
be solved by increasing the column size (use ``BLOB`` or even ``MEDIUMBLOB``). | ||
When using MySQL as the database engine, you can also enable the `strict SQL mode`_ | ||
to get noticed when such an error happens. | ||
|
||
.. _`strict SQL mode`: https://dev.mysql.com/doc/refman/5.0/en/sql-mode.html | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we should link to a more up-to-date version There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Linked to 5.7 version. Thanks. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be:
.. _example-sql-statements:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed. Thanks.