[PATCHES] psql session log

2005-01-01 Thread lsunley
Here is a patch that allows psql to create a session log NOTE - the patch to the makefile is to keep it from constantly building psql.exe as the target psql all by itself is never created as the output executable on OS/2 and Windows is psql.exe. The patch provides for a new command line

[PATCHES] Session log for psql

2005-01-03 Thread lsunley
Here is a patch that allows psql to create a session log NOTE - the patch to the makefile is to keep it from constantly building psql.exe as the target psql all by itself is never created as the output executable on OS/2 and Windows is psql.exe. The patch provides for a new command line

Re: [PATCHES] psql session log

2005-01-03 Thread lsunley
It does happen all over the place... I have equivalent $(X) patches to all the makefiles in src/bin and below Lorne In [EMAIL PROTECTED], on 01/03/05 at 10:47 PM, Peter Eisentraut [EMAIL PROTECTED] said: [EMAIL PROTECTED] wrote: NOTE - the patch to the makefile is to keep it from

[PATCHES] logfile for psql patch update

2005-01-03 Thread lsunley
This update replaces the previous patch for the psql logfile option The print.c routine is also built into src/bin/scripts The ifdef USE_LOGFILE wrapper is to keep out compile errors when the routine is linked into programs other than psql Lorne --

Re: [PATCHES] psql session log

2005-01-04 Thread lsunley
In [EMAIL PROTECTED], on 01/04/05 at 09:49 AM, Bruce Momjian pgman@candle.pha.pa.us said: Peter Eisentraut wrote: [EMAIL PROTECTED] wrote: NOTE - the patch to the makefile is to keep it from constantly building psql.exe as the target psql all by itself is never created as the output

Re: [PATCHES] Session log for psql

2005-01-04 Thread lsunley
There is a way do do it on OS/2 but it requires that you run psql.exe in a shell from the epm editor. That will allow you to feed input typed in the editor to stdin of psql and the editor will capture stdout and stderr from psql. Setting it up is convoluted at best... For people who want a

Re: [PATCHES] [HACKERS] UTF8 or Unicode

2005-02-26 Thread lsunley
In [EMAIL PROTECTED], on 02/26/05 at 07:55 PM, Bruce Momjian pgman@candle.pha.pa.us said: [EMAIL PROTECTED] wrote: Further to my earlier e-mail, there would have to be two lines added to conversion_create.sql for each alternate function name Like: CREATE OR REPLACE FUNCTION

Re: [PATCHES] [HACKERS] UTF8 or Unicode

2005-02-26 Thread lsunley
Further to my earlier e-mail, there would have to be two lines added to conversion_create.sql for each alternate function name Like: CREATE OR REPLACE FUNCTION ascii_to_whatever (INTEGER, INTEGER, CSTRING, CSTRING, INTEGER) RETURNS VOID AS '$libdir/ascmic', 'ascii_to_mic' LANGUAGE 'c' STRICT;

Re: [PATCHES] [HACKERS] UTF8 or Unicode

2005-02-27 Thread lsunley
The routines that do the conversion could have alternate names specified in the conversion_create.sql. There is not reason that I can see why you cannot have two function names pointing to the same routine. like CREATE OR REPLACE FUNCTION ascii_to_mic (INTEGER, INTEGER, CSTRING, CSTRING,

Re: [PATCHES] [HACKERS] UTF8 or Unicode

2005-02-27 Thread lsunley
In [EMAIL PROTECTED], on 02/26/05 at 11:09 PM, Bruce Momjian pgman@candle.pha.pa.us said: Here is an updated version that handles all cases. It does rename the routine names so the primary encoding name is used for the routine names. This will be documented in the release notes if anyone

Re: [PATCHES] [HACKERS] UTF8 or Unicode

2005-02-27 Thread lsunley
Ignore previous e-mail... Missed the patch to the makefile Sorry about that -- --- [EMAIL PROTECTED] --- ---(end of broadcast)---