Use postgres function as second argument to set about squel HOT 9 CLOSED

Yep, you can use a custom value type. Just represent the crypt('my super awesome password', gen_salt('md5')) part as a CryptFunction class or something and then register that value type with squel along with a handler. Then everytime squel encounters an instance of that class it will pass it off to your custom handler to get the string representation.

from squel.

Nope, doesn't work for me:

squel = require('squel')

class RawSql
  constructor: (@sql) ->

squel.registerValueHandler RawSql, (rawSql) ->
  return rawSql.sql

squel.sql = (sql) -> new RawSql(sql)

console.log('%s', squel.insert().into('widgets').set('foo', 42).set('created_at', squel.sql('NOW()')))
# INSERT INTO widgets (foo, created_at) VALUES (42, 'NOW()')

What I need is an unquoted raw value. I think this absolutely must be a part of the library; pretty much every app requires access to NOW().

from squel.

@andreyvit That code works fine for me. I'm running against squel 2.0.0 on node 0.11.10

from squel.

@hiddentao By ‘works fine’, do you mean it produces this?

INSERT INTO widgets (foo, created_at) VALUES (42, NOW())

Anyways, obviously toString isn't the primary use case, and I cannot see how it can possibly work with toParam, given that you give all the output strings to the native driver as values.

from squel.

@andreyvit Yep, that's what I get when I run the code. Have you tried using it with toParam()?

from squel.

Also, just released v3.0.1 which should improve toParam() a little bit.

from squel.

Is this still an issue?

from squel.

No idea, I've stopped using squel. @rubymaniac?

from squel.

Sorry I too stopped using squel. I have no idea if this is still an issue.

from squel.