Make text output more generic

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Make text output more generic
Date: 2002-04-11 09:10:59
Message-ID: GNELIHDDFBOCMGBFGEFOCEBICCAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I'm working on making the SHOW command dump its output as if it were a
select result.

Tom's declared the following as static ("private") methods?

static TextOutputState *begin_text_output(CommandDest dest, char *title);
static void do_text_output(TextOutputState *tstate, char *aline);
static void do_text_output_multiline(TextOutputState *tstate, char *text);
static void end_text_output(TextOutputState *tstate);

I should really move these off somewhere else and make them a bit more
global and generic. I will also use Joe's version (private email) that
should allow more columns in the output. What should I name these
functions? I notice a tendency towards TextDoOutput, TextDoOuputMultiline,
TextEndOutput sort of naming conventions for "global" functions.

Is this a good idea? Where I should put them?

Regards,

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message bpalmer 2002-04-11 10:54:42 Re: 7.3 schedule
Previous Message Mario Weilguni 2002-04-11 08:56:02 Inefficient handling of LO-restore + Patch