fix: use in-memory startedAt for cron job log to survive DB restore

The auto-import wipes the database, destroying the cronJobLog record
created at the start of the job. Now duration is calculated from a
local variable instead of querying the DB, and if the record is gone
a fresh log entry is created in the restored database.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Summit Dental Care
2026-06-26 22:55:07 -04:00
parent 1edf73fdc8
commit 27d9132820
308 changed files with 2570 additions and 1816 deletions

View File

@@ -14,7 +14,9 @@ export const UserFindFirstSelectSchema: z.ZodType<Prisma.UserSelect> = z.object(
username: z.boolean().optional(),
password: z.boolean().optional(),
autoBackupEnabled: z.boolean().optional(),
autoBackupHour: z.boolean().optional(),
usbBackupEnabled: z.boolean().optional(),
usbBackupHour: z.boolean().optional(),
patients: z.boolean().optional(),
appointments: z.boolean().optional(),
staff: z.boolean().optional(),
@@ -44,7 +46,9 @@ export const UserFindFirstSelectZodSchema = z.object({
username: z.boolean().optional(),
password: z.boolean().optional(),
autoBackupEnabled: z.boolean().optional(),
autoBackupHour: z.boolean().optional(),
usbBackupEnabled: z.boolean().optional(),
usbBackupHour: z.boolean().optional(),
patients: z.boolean().optional(),
appointments: z.boolean().optional(),
staff: z.boolean().optional(),