You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -453,14 +453,19 @@ For an example see [shaxbee/go-spatialite](https://github.com/shaxbee/go-spatial
453
453
454
454
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).
455
455
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?
457
459
458
460
Each connection to :memory: opens a brand new in-memory sql database, so if
459
461
the stdlib's sql engine happens to open another connection and you've only
460
462
specified ":memory:", that connection will see a brand new database. A
461
463
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.
0 commit comments