如何授予我的 MacOS 应用程序权限以创建“WAL”文件以使用 journal-mode=WAL 打开 SQLite 数据库？

Question

I'm an experienced programmer, but this is my first MacOS app (on 10.15.2), which needs to read an sqlite db of the user's choice (potentially anywhere on the machine)

At first it wouldn't open the DB 'name.sqlite' file itself; but when I used NSOpenPanel to let the user select it, that worked.

But then the query failed because sqlite3 (via SQLite.swift) was trying to open 'name.sqlite-wal'

os_unix.c:43353: (0) open(/path/to/dbname.lrcat-wal) - Undefined error: 0

If I open the db using the command-line client, and pragma journal-mode=off then the app works fine, but I can't restrict the app based on that - most of the dbs have WAL journalling

I tried turning com.apple.security.app-sandbox false in app.entitlements, but that didn't help.

I tried moving the db to the Pictures folder and turning com.apple.security.assets.pictures.read-write true, but that didn't help.

The unix permissions for db and the containing folder (/tmp in my test) are both good.

Because allowing the user to select the db via the NSOpenPanel allowed me to open the db for reading, I assume there's a similar restriction on the creation of the '-wal' file for writing.

How can I get permission (ideally without bothering the user with details of what a wal file is) to create the file next to the db?

---

Edit: Following TheNextMan's suggestion about sidecar files, I searched again. The WWDC presentation he (guessing the pronoun) linked shows how to use CFBundleDocumentTypes to relate extra extensions with NSIsRelatedItemType for NSFilePresenter , but (as far as I know) I'm not going through that route. I've tried it but it hasn't helped

I also, armed with the "sidecar" search term, found Access sidecar files in a Mac sandboxed app , which looked good but didn't help.

Even better I found the four-year-old unanswered duplicate of my question (if I had enough rep I'd mark this as a duplicate) , SQLite and Sandboxed OSX apps , which includes a quote from Apple documentation App Sandbox Design Guide , saying

Note: In the case of a SQLite journal file, beginning in 10.8.2, journal files, write-ahead logging files, and shared memory files are automatically added to the related items list if you open a SQLite database, so this step is unnecessary.

So apparently it should Just Work™. But it doesn't.

Answer 1

Thank you for this thorough question. I encountered today the same issue as you, fighting the macOS sandbox restrictions. Similar to you, I've already copied the user selected ( NSOpenPanel ) database to my apps temporary folder ( FileManager.default.temporaryDirectory ).
But still I was unable to query the database file: sqlite3_prepare_v2 always returned the os_unix.c:45340: (0) open(/var/folders/.../myDB.db-wal) - Undefined error: 0 message.

As the database already is located in the temporary folder, which definitely is writable by our app (as we copied the database file!), we can simply create the myDB.db-wal file ourselves:

let tmpLocation = /// URL of the SQLite *.db file in a writable directory
let walLocation = tmpLocation.deletingPathExtension().appendingPathExtension("db-wal")
try Data().write(to: walLocation)

Et voilà: opening the DB is working.