John Fawcett
John Fawcett
oh and if all else fails: ```javascript name: { $custom: ['name not like $1', '%test%'] } ```
Maaayyyybe something like: ``` javascript var query = { type: 'select' , table: ['users', 'groups'] , where: { 'users.id': mosql.$('groups.userId') , 'groups.name': 'admin' } }; ```
Hrmmm looking at the Postgres docs, it looks like the where clause for the conflict is for an _index_predicate_, not a proper conditional block. So, that would be a bug...
Ahhhh I see. You can always fallback to using the `$custom` helper in scenarios like this ```javascript { type: 'insert', table: 'entries', values: [ { orgId: '...', otherId: '...', amount:...
Agreed. I'll add a deprecation warning for the old object and string syntaxes.
Yeah, @LinusU I agree there. I'll work on getting this implemented soon
Beautiful!
Oh I was excited to move this repo to use yarn 👍
This is going to require a bit of re-working. Perhaps we should make it a bit more semantic. Currently, we only support simple inserts `("colA", "colB") values ($1, $2)`. The...
Ok yeah I think I'm gonna go with the latter. But I'm gonna sleep on it