Javascript shenanigans
-
That's good to know, but the code I'm about to write using HttpClient is for a data importer than runs as a command line app, so it doesn't matter for my purpose.
-
That may be. The end result is the same: Concurrent write access to the database will result in an error because the db is locked.
-
Each test is a sequence of steps.
-
Concurrent write access to the database will result in an error because the db is locked.
That's because it only implements single writer locks. That in turn is because multi-writer locks are hard to get right (there's a significant amount of OS WTFery in this area); most DBs handle it by having a server that can hold all the locking magic in memory, which is not the same thing at all. Write-heavy loads are better done on a different database system, and can justify the additional complexity involved.
-
@wft said:
you know, when you write a test, you usually imply linear execution
No, I don't know. If your tests fail in a random order in parallel, they are
badgood tests for catching bad code.
ď„when you write a test, you usually imply linear execution
@wft said:Each test is a sequence of steps.
Point taken.
-
End result is still the same: Async is a pain with SQLite. I'm not seeing any of your arguments change my original one.
-
Async is a pain with SQLite.
Because it's really running in the same thread as the code calling it? No shit…
