74618e2b82
* Add option to build with OpenSSL out of the box. Fix thusly exposed bit rot. Although it compiles now, getting this to do something useful is left as an exercise. * Fix Kerberos options to defer checking for required libraries until all the other libraries are checked for. * Change default odbcinst.ini and krb5.srvtab path to PREFIX/etc. * Install work around for Autoconf's install-sh relative path anomaly. Get rid of old INSTL_*_OPTS variables, now that we don't need them anymore. * Use `gunzip -c' instead of g?zcat. Reportedly broke on AIX. * Look for only one of readline.h or readline/readline.h, not both. * Make check for PS_STRINGS cacheable. Don't test for the header files separately. * Disable fcntl(F_SETLK) test on Linux. * Substitute the standard GCC warnings set into CFLAGS in configure, don't add it on in Makefile.global. * Sweep through contrib tree to teach makefiles standard semantics. ... and in completely unrelated news: * Make postmaster.opts arbitrary options-aware. I still think we need to save the environment as well. |
||
|---|---|---|
| .. | ||
| Makefile | ||
| README.string_io | ||
| string_io.c | ||
| string_io.h | ||
| string_io.sql.in | ||
String io module for postgresql. Copyright (C) 1999, Massimo Dal Zotto <dz@cs.unitn.it> This software is distributed under the GNU General Public License either version 2, or (at your option) any later version. These output functions can be used as substitution of the standard text output functions to get the value of text fields printed in the format used for C strings. This allows the output of queries or the exported files to be processed more easily using standard unix filter programs like perl or awk. If you use the standard functions instead you could find a single tuple splitted into many lines and the tabs embedded in the values could be confused with those used as field delimters. My function translates all non-printing characters into corresponding esacape sequences as defined by the C syntax. All you need to reconstruct the exact value in your application is a corresponding unescape function like the string_input defined in the source code. Massimo Dal Zotto <dz@cs.unitn.it>