Changes regarding standard_conforming_strings in postgres

[clsql.git] / ChangeLog

diff --git a/ChangeLog b/ChangeLog
index 8b393e6e9c184ac9cb816ace6a75a5a1e718d3f7..d274bf49daf41d7f7dbcf64dadeebb057b60ef0d 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,21 @@
+2018-04-08 Russ Tyndall <russ@acceleration.net>
+        * sql/db-interface, expressions, fdml, generic-postgres
+       db-mysql/mysql-sql.lisp db-postgresql-socket3/sql.lisp
+
+        - I created a new protocol function (database-escape-backslashes
+          database)
+        - I changed the the generic mysql and postgres databases
+         to return T
+        - I made the postgresql-socket3 backend check for
+         standards_conforming_string which is exposed in the underlying
+         cl-postgres connection
+       - It seems likely that postgresql-socket3 could always return NIL, as
+         cl-postgres would probably handle this escaping anyway
+
+         This replaced some special case code in (database-output-sql (string
+         database))
+
+       
 2018-02-04 Russ Tyndall <russ@acceleration.net>
        * sql/generic-postgres.lisp:    
        Wall times default to being timestamptz in postgresql now.