Releases: chill117/express-mysql-session
Releases · chill117/express-mysql-session
Release v2.1.2
- Fix for issue #97. The new default type for the session data field is now
mediumtext
. This will allow up to 16MB of data to be stored per session. Existing session database tables will keep the old behavior which was limited to 64KB of data per session.
Release v2.1.0
get
,all
, andlength
will now exclude expired sessions. See #89 for more details.- Removed grunt; now using npm run tasks.
- Updated dependencies
Release v2.0.1
- Updated dependencies
Release v2.0.0
- Added new flag
clearExpired
which when set tofalse
will prevent expired sessions from being deleted automatically. The default value istrue
so the default behavior remains unchanged. - Fix for MySQL warning regarding unnecessary
LIMIT 1
clauses. See #82 for more details. - Throw error when defining an unknown column in the
schema
option. See #83 for more details. - Removed deprecated methods (
clone
,closeStore
,defaults
,isObject
,setDefaultOptions
,sync
)
Release v1.3.0
- Updated dependencies
- Fix for issue #78
- Added support for promises in mysql query function; now works with node-mysql2's promise-only connections
Release v1.2.3
- Updated dependencies
MySQLStore.close()
will no longer end the database connection (if provided via constructor). See issue #70 for more information. A new option has been added (endConnectionOnClose
) to control this behavior.
Release v1.2.2
- Updated dependencies
Release v1.2.1
- Updated dependencies
Release v1.2.0
- Removed dependency on mysql-connection-manager; now using connection pooling from node-mysql module.
- Fix for issue #49
Release v1.1.1
- Fix for express-session integration when "cookie.maxAge" is set to NULL.