diff options
| -rw-r--r-- | bug/list | 10 | ||||
| -rw-r--r-- | reference/bug/list | 13 |
2 files changed, 13 insertions, 10 deletions
@@ -12,16 +12,6 @@ ! Copyright update [doc] -! 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. - - Add noexcept to move construction and assignment [c++11] Without noexcept some code (e.g., swap()) may have to resorts to copy. 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, |