diff options
| author | Tom Lane | 2010-06-15 20:29:01 +0000 |
|---|---|---|
| committer | Tom Lane | 2010-06-15 20:29:01 +0000 |
| commit | c0989c67fa8fcc53f8475bbc918e330588628cff (patch) | |
| tree | 42432e90967bebf04b5c1b5829ac2f370eef3d3d /contrib/dblink/sql | |
| parent | 77a4c51af80819c3bcd581d9237f5c47e68393a6 (diff) | |
Change the interpretation of the primary_key_attnums parameter of
dblink_build_sql_insert() and related functions. Now the column numbers
are treated as logical not physical column numbers. This will provide saner
behavior in the presence of dropped columns; furthermore, if we ever get
around to allowing rearrangement of logical column ordering, the original
definition would become nearly untenable from a usability standpoint.
Per recent discussion of dblink's handling of dropped columns.
Not back-patched for fear of breaking existing applications.
Diffstat (limited to 'contrib/dblink/sql')
| -rw-r--r-- | contrib/dblink/sql/dblink.sql | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contrib/dblink/sql/dblink.sql b/contrib/dblink/sql/dblink.sql index b15c4ddaf0c..a6d7811bfc8 100644 --- a/contrib/dblink/sql/dblink.sql +++ b/contrib/dblink/sql/dblink.sql @@ -430,11 +430,11 @@ ALTER TABLE test_dropped ADD COLUMN col3 VARCHAR(10) NOT NULL DEFAULT 'foo', ADD COLUMN col4 INT NOT NULL DEFAULT 42; -SELECT dblink_build_sql_insert('test_dropped', '2', 1, +SELECT dblink_build_sql_insert('test_dropped', '1', 1, ARRAY['1'::TEXT], ARRAY['2'::TEXT]); -SELECT dblink_build_sql_update('test_dropped', '2', 1, +SELECT dblink_build_sql_update('test_dropped', '1', 1, ARRAY['1'::TEXT], ARRAY['2'::TEXT]); -SELECT dblink_build_sql_delete('test_dropped', '2', 1, +SELECT dblink_build_sql_delete('test_dropped', '1', 1, ARRAY['2'::TEXT]); |