Skip to content

Commit e770ec5

Browse files
committed
fix/511
Closes #511 [skip ci]
1 parent 578beef commit e770ec5

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

Diff for: README.md

+8-3
Original file line numberDiff line numberDiff line change
@@ -453,14 +453,19 @@ For an example see [shaxbee/go-spatialite](https://github.com/shaxbee/go-spatial
453453
454454
Yes for readonly. But, No for writable. See [#50](https://github.com/mattn/go-sqlite3/issues/50), [#51](https://github.com/mattn/go-sqlite3/issues/51), [#209](https://github.com/mattn/go-sqlite3/issues/209), [#274](https://github.com/mattn/go-sqlite3/issues/274).
455455
456-
- Why is it racy if I use a `sql.Open("sqlite3", ":memory:")` database?
456+
- Why I'm getting `no such table` error?
457+
458+
Why is it racy if I use a `sql.Open("sqlite3", ":memory:")` database?
457459

458460
Each connection to :memory: opens a brand new in-memory sql database, so if
459461
the stdlib's sql engine happens to open another connection and you've only
460462
specified ":memory:", that connection will see a brand new database. A
461463
workaround is to use "file::memory:?mode=memory&cache=shared". Every
462-
connection to this string will point to the same in-memory database. See
463-
[#204](https://github.com/mattn/go-sqlite3/issues/204) for more info.
464+
connection to this string will point to the same in-memory database.
465+
466+
For more information see
467+
* [#204](https://github.com/mattn/go-sqlite3/issues/204)
468+
* [#511](https://github.com/mattn/go-sqlite3/issues/511)
464469

465470
- Reading from database with large amount of goroutines fails on OSX.
466471

0 commit comments

Comments
 (0)