From 1f04379d84abd01390add103092127584d51dc9c Mon Sep 17 00:00:00 2001 From: Alexandre Roux Date: Sat, 20 Jul 2024 18:39:55 +0200 Subject: [PATCH] doc for issue #1118 --- sqflite/doc/usage_recommendations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sqflite/doc/usage_recommendations.md b/sqflite/doc/usage_recommendations.md index ab4b4cfa..518cb87f 100644 --- a/sqflite/doc/usage_recommendations.md +++ b/sqflite/doc/usage_recommendations.md @@ -19,8 +19,8 @@ Access *should* be done in the main isolate: * [sqflite_common_ffi](https://pub.dev/packages/sqflite_common_ffi) access is made in a separate isolate. Many people have asked about access from another isolate and unfortunately I don't have a good answer for that. -It **should** work although I have not tested it much and I have avoid it (for example by saving the temporary data read -in a file that I handle later in the main isolate. One common usage +It **should** work although I have not tested it much and I have avoided it (for example by saving the temporary data read +in a file that I handle later in the main isolate). One common usage on Android and iOS is to have access from a push notification isolate or scheduled task. * Good if you can avoid it and only limit to this case (background notification / scheduled task) * In both isolates