Kevin Leung

Perhaps it is actually easier to support transaction by moving pooling out of the node driver (and perhaps do the pooling in tink-level)? cc @andyli

+1 just stumbled into this. Just to add, this doesn't happen inside type parameters (i.e. `Foo`)

Just stumbled into a situation where I need to write this SQL: (basically to sort out the correct chatroom that consist of the exact two members) ```sql SELECT chatroom.id, count(*)...

Recently I wrote something to sort by an alias, something like this: ```haxe db.table.select({sort: table.col1}) .orderBy(fields -> [{field: cast EField(null, 'sort'), order: Desc}]); ``` Note that there is no way...

Can we have `having` which gets the same `fields` object as `orderby`/`groupby` first? So at least we can go on (with hacks like `cast EField(null, 'sort')`)

> Or maybe use the select macro to name it as the last argument in Filter used for order/group/having: I guess this API looks cleaner. And maybe default the var...

Can you try adding `from Int` to `Id`?

Is it like `Sub` and `Function` in VB6? The former returns nothing while the former returns something?

So yeah, `CallProcedure` and `@:procedure` is what you need.

Functions are dealt with `Expr.ECall`, just like any built-in SQL functions like `IF(cond, t, f)`