aboutsummaryrefslogtreecommitdiff
path: root/src/interfaces/python/tutorial/basics.py
diff options
context:
space:
mode:
authorBarry Lind <barry@xythos.com>2003-01-14 05:05:26 +0000
committerBarry Lind <barry@xythos.com>2003-01-14 05:05:26 +0000
commit88e524063ab68a0bb287c5c0545e11a8164cd613 (patch)
tree691ef33e141c7ea4697d7370c0ed6829fc34de05 /src/interfaces/python/tutorial/basics.py
parent956762a546b853a8fbd70377ebf63d4e61f84e36 (diff)
downloadpostgresql-88e524063ab68a0bb287c5c0545e11a8164cd613.tar.gz
postgresql-88e524063ab68a0bb287c5c0545e11a8164cd613.zip
Patch from Kris Jurka to improve the performance of getImportedKeys().
Use explicit joins to avoid using the genetic query optimizer. Also fixed a regression test that was failing to compile. This change also cleans up how key names are reported as per: A change to the value of the FK_NAME column. Currently the returned value is the triggers arguments which look like "<unnamed>\000t2\000t1\000UNSPECIFIED\000a\000a\000" This was required for server versions < 7.3 when a user did not supply constraint names. Every constraint was named "<unnamed>" . 7.3 has enforced unique constraint names per table so unnamed foreign keys will have different names "$1", "$2" and so on. I've used logic along the lines of the following to preserve the unique names in the original scheme, but allow people who go to the trouble of naming their constraints to see them: if (triggerargs.startsWith("<unnamed>")) { fkname = [the whole ugly trigger args name originally used]; } else { fkname = [the actual fk name]; } Modified Files: jdbc/org/postgresql/jdbc1/AbstractJdbc1DatabaseMetaData.java jdbc/org/postgresql/test/jdbc2/optional/ConnectionPoolTest.java
Diffstat (limited to 'src/interfaces/python/tutorial/basics.py')
0 files changed, 0 insertions, 0 deletions