Check that prepared statements are working as expected.

[chanks]

See #74.

[joevandyk]

tanga_dev=# prepare test  as select 'now'::timestamptz;
PREPARE
tanga_dev=# execute test;
          timestamptz
-------------------------------
 2015-01-13 09:13:05.742936-08
(1 row)

tanga_dev=# execute test;
          timestamptz
-------------------------------
 2015-01-13 09:13:05.742936-08
(1 row)

Seems like there would be a problem if using prepared statements.

[joevandyk]

Although:

tanga_dev=# prepare test  as select 'now()'::timestamptz;
PREPARE
tanga_dev=# execute test;
          timestamptz
-------------------------------
 2015-01-13 09:20:51.518569-08
(1 row)

tanga_dev=# execute test;
          timestamptz
-------------------------------
 2015-01-13 09:20:51.518569-08
(1 row)

I don't know much about prepared statements yet.

[edit]

I see, removing the quotes is the trick:

tanga_dev=# prepare test  as select now()::timestamptz;
PREPARE
tanga_dev=# execute test;
              now
-------------------------------
 2015-01-13 09:23:24.448843-08
(1 row)

tanga_dev=# execute test;
              now
-------------------------------
 2015-01-13 09:23:25.384618-08
(1 row)

[johto]

Yeah, the difference is that one is a function call evaluated during runtime, and the other one is a literal evaluated during prepare. If the problem can't be reproduced in Ruby, I'm guessing it doesn't do server-side prepared statements.

The cast to timestamptz for now() is unnecessary, since it's guaranteed to return a timestamptz.

[chanks]

Going through old issues and can't replicate this one. I suppose the switch to now() fixed it. Thanks, though!