AMT-Cheif
/
drift
mirror of https://github.com/AMT-Cheif/drift.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

typos

This commit is contained in:
Robin Braun 2020-04-16 11:52:28 +02:00 committed by GitHub
parent 3a53c60132
commit 1672fbbfe8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/content/en/docs/Advanced Features/isolates.md
View File

@ -139,7 +139,7 @@ a setup where you have three or more threads:
- A foreground isolate, probably for Flutter
- Another background isolate, which could be used for networking.
You can the read data from the foreground isolate or start query streams, similar to the example
You can then read data from the foreground isolate or start query streams, similar to the example
above. The background isolate would _also_ call `MoorIsolate.connect` and create its own instance
of the generated database class. Writes to one database will be visible to the other isolate and
also update query streams.
@ -153,7 +153,7 @@ All moor features are supported on background isolates and work out of the box.
- Batched updates and inserts
- Custom statements or those generated from an sql api
Please note that, will using a background isolate can reduce lag on the UI thread, the overall
Please note that, while using a background isolate can reduce lag on the UI thread, the overall
database is going to be slower! There's a overhead involved in sending data between
isolates, and that's exactly what moor has to do internally. If you're not running into dropped
frames because of moor, using a background isolate is probably not necessary for your app.