Hilton Campbell

@barbasevich I still have to specify them one-by-one with that.

`Cursor`'s subscript uses the column type to decide what kind of binding to use for the value: ``` public subscript(idx: Int) -> Binding? { switch sqlite3_column_type(handle, Int32(idx)) { case SQLITE_BLOB:...

It's not done, but this is [what I'm thinking](https://github.com/hiltonc/SQLite.swift/commit/6d7e44684343cc6899dac70b087a01cd9b8c2b63). I really don't like how verbose it is, but I can't figure out a tighter way to make the compiler happy.

I guess it depends on what use cases SQLite.swift should support. I agree, if you use SQLite.swift all the way, you won't run into trouble. But sometimes you want to...

This is the top crash in our app.

I would like this behavior as well. Currently the best I can do is put the local packages in a top-level folder, like: ``` /MyProject /Packages /Package1 /Package2 ``` What...

I don't see an obvious change to the API, other than accepting "" for `group` or `localPackageGroup`. I'm not aware of that being a precedent anywhere else in the API...

@yonaskolb Thanks, I added support for both options in #1413.

@OmranK yes, it should enable you to do that

@yonaskolb I've resolved conflicts, tests pass, and I manually verified both configuration options.