connect-pg-simple
Advanced tools
connect-pg-simple - npm Package Versions
Changelog
3.0.1
- Fix: If the
pginstance used is created by this module, then this module should also close it onclose()
Changelog
3.0.0
- Improvement: Rather than randomly cleaning up expired sessions that will now happen at the
options.pruneSessionIntervaldefined interval. - Breaking change: Clients now need to close the session store to gracefully shut down their app as the pruning of sessions can't know when the rest of the app has stopped running and thus can't know when to stop pruning sessions if it itsn't told so explicitly through thew new
close()method – or by deactivating the automatic pruning by settingingoptions.pruneSessionIntervaltofalse. If automatic pruning is disabled the client needs to callpruneSessions()manually or otherwise ensure that old sessions are pruned.
Changelog
2.3.0
- Fix regression: No longer default to
publicschema, as added in2.2.0, but rather default to the pre-2.2.0behavior of no defined schema. This to ensure backwards compatibility with the2.xbranch, per semantic versioning best practise.
Changelog
2.2.1
- Hotfix: Update
require('pg')to match package.json, thanks for reporting @dmitriiabramov
Changelog
2.2.0
- New: Now possibly to set another schema than the default
- Change: Now using the
pgdependency again rather thanpg.jsas the latter will be discontinued aspgnow fills its role
Changelog
2.0.0
- Backwards incompatible change: Support for Express 4 means that Express 3 apps (and similar for Connect apps) should send
express.sessionto the module rather than justexpress. - Dependency change: The database module is now pg.js rather than pg – same library, but without compilation of any native bindings and thus less delay when eg. installing the application from scratch.