summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorMichael Meskes <meskes@postgresql.org>2015-02-10 12:00:13 +0100
committerMichael Meskes <meskes@postgresql.org>2015-02-10 12:04:10 +0100
commit1f393fc923ec77f25fd37e16fd8ccb480df82ebb (patch)
treee771707dfd308ec99087cdfb601bdb74c07ef032 /doc/src
parent025c02420de990c15a90e9e3f86fcfbc5b59ee88 (diff)
Fixed array handling in ecpg.
When ecpg was rewritten to the new protocol version not all variable types were corrected. This patch rewrites the code for these types to fix that. It also fixes the documentation to correctly tell the status of array handling.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/ecpg.sgml11
1 files changed, 7 insertions, 4 deletions
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 1b34a6f75fb..76677924700 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -1377,10 +1377,13 @@ EXEC SQL END DECLARE SECTION;
<title>Arrays</title>
<para>
- SQL-level arrays are not directly supported in ECPG. It is not
- possible to simply map an SQL array into a C array host variable.
- This will result in undefined behavior. Some workarounds exist,
- however.
+ Multi-dimensional SQL-level arrays are not directly supported in ECPG.
+ One-dimensional SQL-level arrays can be mapped into C array host
+ variables and vice-versa. However, when creating a statement ecpg does
+ not know the types of the columns, so that it cannot check if a C array
+ is input into a corresponding SQL-level array. When processing the
+ output of a SQL statement, ecpg has the necessary information and thus
+ checks if both are arrays.
</para>
<para>