re
/
go-sqlcipher
forked from mirror/go-sqlcipher
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #376 from tych0/memory-faq 

add a FAQ entry about :memory: races
This commit is contained in:
mattn 2017-01-27 09:02:38 +09:00 committed by GitHub
parent 7ed900a7c4 ded1ba664d
commit ce9149a3c9
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -68,6 +68,15 @@ FAQ
Yes for readonly. But, No for writable. See #50, #51, #209. Yes for readonly. But, No for writable. See #50, #51, #209.
* Why is it racy if I use a `sql.Open("sqlite", ":memory:")` database?
Each connection to :memory: opens a brand new in-memory sql database, so if
the stdlib's sql engine happens to open another connection and you've only
specified ":memory:", that connection will see a brand new database. A
workaround is to use "file::memory:?mode=memory&cache=shared". Every
connection to this string will point to the same in-memory database. See
#204 for more info.
License License
------- -------