From c4c9b52400685462812403566bd46e33dd812616 Mon Sep 17 00:00:00 2001
From: glacialcascade <11969863+glacialcascade@users.noreply.github.com>
Date: Sat, 8 Jun 2024 15:56:53 -0400
Subject: [PATCH] add comment to solve.txt

---
 user-1/solve.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/user-1/solve.txt b/user-1/solve.txt
index 334de3a7..ffde645c 100644
--- a/user-1/solve.txt
+++ b/user-1/solve.txt
@@ -52,6 +52,9 @@ response.
 So, we can assume that the server is hard-coded to check id=1, which
 gives sense given the challenge title, description, etc.
 
+(Another simple way to conclude this is by using a single ", which yields
+the error « unrecognized token: """" WHERE id=1" ».)
+
 We can use the FOREIGN KEY constraint to our advantage, given
 the ON UPDATE CASCADE keyword.