852d2cf304
* @remindme bot support support reminders via @remindme bot, just like @delete bot * minor cleanup * minor query cleanup * add db migration * various fixes and updates: * hasNewNotes implementation * actually return notification component in ui * delete reminder and job on item delete * other goodies * refactor to use prisma for deleting existing reminder * * switch to deleteMany to delete existing Reminders upon edit/delete of post to satisfy prisma * update wording in form toast for remindme bot usage * update wording in the push notification sent * transactional reminder inserts and expirein * set expirein on @delete too --------- Co-authored-by: Keyan <34140557+huumn@users.noreply.github.com> Co-authored-by: keyan <keyan.kousha+huumn@gmail.com>
20 lines
715 B
SQL
20 lines
715 B
SQL
-- CreateTable
|
|
CREATE TABLE "Reminder" (
|
|
"id" SERIAL NOT NULL,
|
|
"created_at" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
|
|
"userId" INTEGER NOT NULL,
|
|
"itemId" INTEGER NOT NULL,
|
|
"remindAt" TIMESTAMP(3) NOT NULL,
|
|
|
|
CONSTRAINT "Reminder_pkey" PRIMARY KEY ("id")
|
|
);
|
|
|
|
-- CreateIndex
|
|
CREATE INDEX "Reminder.userId_reminderAt_index" ON "Reminder"("userId", "remindAt");
|
|
|
|
-- AddForeignKey
|
|
ALTER TABLE "Reminder" ADD CONSTRAINT "Reminder_userId_fkey" FOREIGN KEY ("userId") REFERENCES "users"("id") ON DELETE CASCADE ON UPDATE CASCADE;
|
|
|
|
-- AddForeignKey
|
|
ALTER TABLE "Reminder" ADD CONSTRAINT "Reminder_itemId_fkey" FOREIGN KEY ("itemId") REFERENCES "Item"("id") ON DELETE CASCADE ON UPDATE CASCADE;
|