Stephen Celis

> As a fair amount of the code of this library is unsafe, and at the light of this issue, I wonder if it wouldn't be better to defensively test...

@bbethke We unfortunately haven't been able to track down the right Swift runtime code for this yet 😞 Is the workaround mentioned above sufficient in the meantime?

Hey @inamiy! We recently wanted to reach for this exact functionality and were a little surprised it didn't exist, given the number of operator overloads defined. That said, we're a...

> So I think, in essence, we want to first have this PR than L211 (since it's simpler), and may want to reconsider too many overload issue for both this...

Expressions are quoted by default. What you want is to use is `Expression.init(literal:)` or `Expression.init(_:_:)`: https://github.com/stephencelis/SQLite.swift/blob/master/SQLite/Typed/Expression.swift#L38-L40 I think this snippet helper should work: ``` swift func snippet(column: Expression) -> Expression...

Aliasing functionality has been limited to tables during the rewrite, where the functionality is required for joins to work. Aliasing column/expressions doesn't seem to help in our expression layer, although...

My experimentation showed that these aliases are actually meaningless outside of the SQLite console. You should be able do do this, though: ``` swift let a = Table("a") let b...

@groue SQLite.swift has a PR that's been open for awhile that addresses this: https://github.com/stephencelis/SQLite.swift/pull/289 It needs a shepherd to help bring it to completion, though.

@kdubb has reopened the following PR: https://github.com/stephencelis/SQLite.swift/pull/411 I encourage anyone that wants to use a connection pool to check it out.

Re: > Might be an argument for going towards the blocks/closures style. And: > it'd be far better to wrap them in a transaction and ensure that for the duration...