From 4701df22146e4e4fc0c7fe58903fbd0482defcb5 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Fri, 23 Jan 2015 10:53:46 +0200 Subject: Handle name truncation in PostgreSQL --- doc/odb-epilogue.1 | 3 ++- doc/odb-epilogue.xhtml | 7 ++++--- 2 files changed, 6 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/odb-epilogue.1 b/doc/odb-epilogue.1 index 6968767..0818bf8 100644 --- a/doc/odb-epilogue.1 +++ b/doc/odb-epilogue.1 @@ -41,8 +41,9 @@ can be .BR column , .BR index , .BR fkey , +.BR sequence , or -.BR sequence . +.BR statement . On the other hand, if we want our regular expressions to apply to all SQL names, then we use the .B --sql-name-regex diff --git a/doc/odb-epilogue.xhtml b/doc/odb-epilogue.xhtml index da3fdef..c108df8 100644 --- a/doc/odb-epilogue.xhtml +++ b/doc/odb-epilogue.xhtml @@ -21,9 +21,10 @@ --kind-regex options, where kind can be table, column, index, - fkey, or sequence. On the - other hand, if we want our regular expressions to apply to all SQL - names, then we use the --sql-name-regex option.

+ fkey, sequence, or + statement. On the other hand, if we want our + regular expressions to apply to all SQL names, then we use the + --sql-name-regex option.

The interaction between the higher and lower level transformations is as follows. Prefixes and suffixes are added first. Then the -- cgit v1.1