From: Karl O. Pinc <kop@karlpinc.com>
Date: Fri, 13 Sep 2024 18:54:36 +0000 (-0500)
Subject: Explain why we can safely use the SQLHander to process the SQL edit form
X-Git-Url: https://papio.biology.duke.edu/gitweb/?a=commitdiff_plain;h=66d25d4fa752845f5294218d275e4b5648b2ec3d;p=pgwui_sql

Explain why we can safely use the SQLHander to process the SQL edit form
---

diff --git a/src/pgwui_sql/views/sql.py b/src/pgwui_sql/views/sql.py
index 95ccd2c..565731e 100644
--- a/src/pgwui_sql/views/sql.py
+++ b/src/pgwui_sql/views/sql.py
@@ -258,6 +258,9 @@ def sql_view(request):
              renderer='pgwui_sql:templates/sql_edit.mak')
 @auth_base_view
 def sql_edit_view(request):
+    # We don't worry about this contacting the db to execute sql
+    # because pgwui_core.core does not try to alter the db until
+    # the hidden "action" POST variable is something other than ''.
 
     uh = SQLHandler(request).init()
     response = pgwui_core.core.UploadEngine(uh).run()