Kevin Leung

I thought the following will work with inline markup, but it doesn't ```html {#if value #end} ``` Failing with `Invalid expression`

Just hit a use case that I want to avoid badly-named column names to spread into my code base. Which is a better choice: `@:column('foo')` or `@:name('foo')` or else?

I am mainly looking for transaction right now. And maybe ALTER table later. I just dunno if we can support all SQL syntax, if not we might want to let...

A few notes on implementation: 1. Generated field should not appear in a `insert` query 2. But it should appear in the result of a `select` query 3. I think...

Maybe my description was confusing, I meant this: 1. `$type(db.Table.insertOne)` => `{nonComputed:String}->Promise` 1. `$type(db.Table.first())` => `Promise` 1. `db.Table.select($type({...}))` => `{?nonComputed, ?computed}` So what I mean is simply: computed values should...

Computed columns can be used for (speeding up) aggregation. So no, I don't think they are equivalent.

Apparently something is unable to infer the type parameter of `tink.pure.Vector`. Explicitly type-hinting fixes it: ``

Is there any update about transactions?

> But you'll have to be careful to operate on the argument of `f` rather than object that you called `transaction` on. This should be fine as long as the...

I am not sure if it is related, but some time ago I added true streaming support to the node driver, which involves manually obtaining a connection from the pool...