new go1.8 feature

[mattn]

Closing #346

On Conn

• BeginContext(ctx) (tx,err) found in ConnBeginContext
• PrepareContext(ctx, query) (stmt,err) found in ConnPrepareContext
• ExecContext(ctx, query, []namedvalue) (res, err) found in ExecerContext
• Ping(ctx) err found in Pinger
• QueryContext(ctx, query, []namedvalue) (rows, err) found in QueryerContext

On "Stmt"

• ExecContext(ctx, []namedvalue) (res, err) found in StmtExecContext
• QueryContext(ctx, []namedvalue) (rows, err) found in StmtQueryContext

On "Rows"

• HasNextResultSet() bool found in RowsNextResultSet
• NextResultSet() error found in RowsNextResultSet
• ColumnTypeDatabaseTypeName(index int) (name string)
• ColumnTypeLength(index int) (length int64, ok bool)
• ColumnTypeNullable(index int) (nullable, ok bool)
• ColumnTypePrecisionScale(index int) (precision, scale int64, ok bool)
• ColumnTypeScanType(index int) reflect.Type

[coveralls]

Coverage decreased (-1.9%) to 59.806% when pulling 29b191f on ping into 86681de on master.

[coveralls]

Coverage decreased (-1.9%) to 59.806% when pulling 025b917 on ping into 86681de on master.

[coveralls]

Coverage decreased (-1.7%) to 60.0% when pulling 57eaf4c on ping into 86681de on master.

[coveralls]

Coverage increased (+1.1%) to 62.773% when pulling 57eaf4c on ping into 86681de on master.

[coveralls]

Coverage increased (+1.1%) to 62.773% when pulling 57eaf4c on ping into 86681de on master.

[coveralls]

Coverage increased (+1.1%) to 62.773% when pulling 57eaf4c on ping into 86681de on master.

[coveralls]

Coverage increased (+1.1%) to 62.773% when pulling 57eaf4c on ping into 86681de on master.

[coveralls]

Coverage increased (+1.1%) to 62.773% when pulling 57eaf4c on ping into 86681de on master.

[mattn]

I decide NOT to support NextResultSet/HasNextResultSet because the go's multiple result is not same as sqlite's one.

[azavorotnii]

@mattn is there some workaround for NextResultSet usage? Currently, if I have multiple selects in same Query() it returns only last select rows.

[mattn]

When I looked at database / sql before, it seemed impossible to implement multiple-resultset for sqlite3 because the behavior of multiple-resultset of database/sql is different from the one expected. But now I looked it, I seems possible to implement. (Seems HasNextResultSet is gone, but not problem)

[mattn]

#497