aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/json.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-08-09 13:46:34 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-08-09 13:46:34 -0400
commit9da86753735ab89b0ee685aea985b25c4218ca0b (patch)
treee58d18f8bfc968aefa6ce7e46ec39e1f43364fef /src/backend/utils/adt/json.c
parentf25e0bf5e0af01a687395a76e676dadeb4a60d0a (diff)
downloadpostgresql-9da86753735ab89b0ee685aea985b25c4218ca0b.tar.gz
postgresql-9da86753735ab89b0ee685aea985b25c4218ca0b.zip
Reject duplicate column names in foreign key referenced-columns lists.
Such cases are disallowed by the SQL spec, and even if we wanted to allow them, the semantics seem ambiguous: how should the FK columns be matched up with the columns of a unique index? (The matching could be significant in the presence of opclasses with different notions of equality, so this issue isn't just academic.) However, our code did not previously reject such cases, but instead would either fail to match to any unique index, or generate a bizarre opclass-lookup error because of sloppy thinking in the index-matching code. David Rowley
Diffstat (limited to 'src/backend/utils/adt/json.c')
0 files changed, 0 insertions, 0 deletions