jebas / connect-pg Goto Github PK

this.getClient(function(err, client, done) {
  if (err) return fn(err);

  client.query('DELETE FROM ' + _this.table + ' WHERE sid = $2;', [ sid ], function(err) {
    done();
    if (err) return fn(err);
    fn();
  });
});

Postgres can't find $1 parameter and invoke error. If you replace $2 to $1 it will work.

Thanks.

As of version 1.0 of node-postgres, the pg.connect callback now returns a 'done' callback which one needs to use to return the client object to the connection pool.

var pg = require('pg');

function pgConnect (callback) {
    pg.connect('tcp://nodepg:password@localhost/pgstore',
        function (err, client, done) {
            if (err) {
                console.log(JSON.stringify(err));
            }
            if (client) {
                callback(client);
                done();
            }
        }
    );
};

Hi there,

I'm using express.js in conjunction with connect-pg.
I want these sessions to expire within a reasonable amount of time, so I tried setting them to 1 hour, just for kicks.

    app.use(express.session({
        store: new pgStore(pgConnect),
        maxAge  : new Date(Date.now() + 3600000), //1 Hour
        expires : new Date(Date.now() + 3600000), //1 Hour
        secret: '@ky.jF8VBhR2[?tMqR9M6N4;Ek9b%tChxPtoTWFF'
    }));

It seems that the maxAge and expires that are set in express are not honored in connect-pg.
Below is a sample row from the output from psql when I take a look at the contents of the session table

"cookie":{"originalMaxAge":null,"expires":null,"httpOnly":true,"path":"/"

I believe it's a bug, but then again I'm new to node, so I could be missing something.

I already had a working code storing connect session to a noSQL backend. I wanted switch connect-pg. But each call generates a new session. What could be the reason? Seems everything works, even the data that I attached to the session is stored in the database, but each call generates a new session. Thanks.

What's the status of this project?