From bb6b5ce2caa795b811bd0ef4bd1e22880133b699 Mon Sep 17 00:00:00 2001 From: kleydon Date: Thu, 22 Sep 2022 14:00:43 -0600 Subject: [PATCH] style: updated comment --- src/lib/prisma-session-store.ts | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/lib/prisma-session-store.ts b/src/lib/prisma-session-store.ts index 0c78a28..61eb8a3 100755 --- a/src/lib/prisma-session-store.ts +++ b/src/lib/prisma-session-store.ts @@ -70,15 +70,15 @@ export class PrismaSessionStore extends Store { // to touch() or set(), using the same session id. // This can occur, for instance, when a browser is loading // a page with multiple resources in parallel. - // It is not yet clear whether this is an issue within: - // * SQLite (see https://stackoverflow.com/questions/4060772/sqlite-concurrent-access), - // * express-session - // * Prisma - // * Possibly a combination. + // The issue may simply be an issue with SQLite + // (see https://stackoverflow.com/questions/4060772/sqlite-concurrent-access), + // but it hasn't yet been isolated. It is possible that express-session or prisma + // are alternately / additionally implicated. // // Until there is a long-term solution, this library offers a work-around, // wherein only a single invocation of set() (or touch()) for a given session id // may be executed at a time. + // // If necessary, this workaround may be disabled by setting the following // PrismaSessionStore options to true: // * enableConcurrentSetInvocationsForSameSessionID