CloudKitTests userRead vs userWrite

[seanwoodward]

Should closures containing queries which only select values be userRead?

[mbrandonw]

Yes, potentially. We need to audit this, but we install certain functions in the write connection of the pool and those helpers will not be available from the read transactions. However, there’s a chance we aren’t using those helpers from read transactions.

Either way, we could try converting the writes that can be reads and run tests to see what happens. We are starting to get decent coverage now.

[seanwoodward]

read or write the create and drop trigger statements are called and logged.

[seanwoodward]

the sync engine and db isn't/shouldn't be created in the context of the read operation anyway.

[seanwoodward]

Or, does PRAGMA query_only = 1 change the results when querying sqlite_temp_master? Hmm.

[seanwoodward]

Or a function of DatabasePool and a possible separate connection?

[seanwoodward]

Yep, that is exactly it. Not

...a possible separate connection

Definitely separate connections. DatabasePool uses a single writer and a Pool of readers. Separate connections means different sqlite_temp_master tables. I'm used to running tests on DatabaseQueue. Thank you for your patience.