[postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name

[PostGIS]

#748: shp2pgsql use wrong schema name
-----------------------+----------------------------------------------------
 Reporter:  aperi2007  |       Owner:  pramsey      
     Type:  defect     |      Status:  new          
 Priority:  medium     |   Milestone:  PostGIS 2.0.0
Component:  postgis    |     Version:  trunk        
 Keywords:             |  
-----------------------+----------------------------------------------------

Comment(by robe):

 Jeff,

 I'm having trouble running the new regress tests on my windows install --
 its giving these complaints:


 loader/TSTPolygongrep: invalid option -- m
 Usage: grep [OPTION]... PATTERN [FILE]...
 Try `grep --help' for more information.


 I'm also now getting failure on tickets regress.  I'm investigating that
 one.

 I vaguely recall we had issues with grep in mingw before.  I think the
 solution might have been to use the long name of the option rathr than the
 short-name.

 FWIW here is what my mingw grep output returns:

 {{{
 Usage: grep [OPTION]... PATTERN [FILE] ...
 Search for PATTERN in each FILE or standard input.
 Example: grep -i 'hello world' menu.h main.c

 Regexp selection and interpretation:
   -E, --extended-regexp     PATTERN is an extended regular expression
   -F, --fixed-strings       PATTERN is a set of newline-separated strings
   -G, --basic-regexp        PATTERN is a basic regular expression
   -e, --regexp=PATTERN      use PATTERN as a regular expression
   -f, --file=FILE           obtain PATTERN from FILE
   -i, --ignore-case         ignore case distinctions
   -w, --word-regexp         force PATTERN to match only whole words
   -x, --line-regexp         force PATTERN to match only whole lines
   -z, --null-data           a data line ends in 0 byte, not newline

 Miscellaneous:
   -s, --no-messages         suppress error messages
   -v, --invert-match        select non-matching lines
   -V, --version             print version information and exit
       --help                display this help and exit
       --mmap                use memory-mapped input if possible

 Output control:
   -b, --byte-offset         print the byte offset with output lines
   -n, --line-number         print line number with output lines
   -H, --with-filename       print the filename for each match
   -h, --no-filename         suppress the prefixing filename on output
   -q, --quiet, --silent     suppress all normal output
       --binary-files=TYPE   assume that binary files are TYPE
                             TYPE is 'binary', 'text', or 'without-match'.
   -a, --text                equivalent to --binary-files=text
   -I                        equivalent to --binary-files=without-match
   -d, --directories=ACTION  how to handle directories
                             ACTION is 'read', 'recurse', or 'skip'.
   -r, --recursive           equivalent to --directories=recurse.
   -L, --files-without-match only print FILE names containing no match
   -l, --files-with-matches  only print FILE names containing matches
   -c, --count               only print a count of matching lines per FILE
   -Z, --null                print 0 byte after FILE name

 Context control:
   -B, --before-context=NUM  print NUM lines of leading context
   -A, --after-context=NUM   print NUM lines of trailing context
   -C, --context[=NUM]       print NUM (default 2) lines of output context
                             unless overridden by -A or -B
   -NUM                      same as --context=NUM
   -U, --binary              do not strip CR characters at EOL (MSDOS)
   -u, --unix-byte-offsets   report offsets as if CRs were not there
 (MSDOS)

 `egrep' means `grep -E'.  `fgrep' means `grep -F'.
 With no FILE, or when FILE is -, read standard input.  If less than
 two FILEs given, assume -h.  Exit status is 0 if match, 1 if no match,
 and 2 if trouble.

 Report bugs to <bug-gnu-utils at gnu.org>.

 }}}

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/748#comment:23>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.