summaryrefslogtreecommitdiff
path: root/reference/bug
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2015-01-23 10:53:46 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2015-01-23 10:53:46 +0200
commit52785dde4b58f2edacdccf7d8557fdf41cb33781 (patch)
tree4e019c3a4dfa069b71e3a0de944b3864939ce842 /reference/bug
parentbfdc0959e9feadd7e4c5d64a525873fcccabed51 (diff)
Handle name truncation in PostgreSQL
Diffstat (limited to 'reference/bug')
-rw-r--r--reference/bug/list13
1 files changed, 13 insertions, 0 deletions
diff --git a/reference/bug/list b/reference/bug/list
index 8d95506..ba7819e 100644
--- a/reference/bug/list
+++ b/reference/bug/list
@@ -1,3 +1,16 @@
++ Statement name truncation in PostgreSQL [pgsql]
+
+ There seems to be a limit on the prepared statement name in PG. The result
+ is that the names are no longer unique (statement already exists error).
+ What we can do to help with that is put the statement kind (perists, find,
+ etc.) part at the beginning of the name rather than at the end as we do
+ now.
+
+ See email from <abellina@gmail.com>/11-Jun-2014.
+
+ In addition, implemented warning when an SQL name (statements and others)
+ exceed the default limit of 63 characters.
+
+ stderr_tracer doesn't trace statement preparation [2.4.0]
If a statement is invalid, then it will fail during preparation. However,