Make text output more generic
| От | Christopher Kings-Lynne |
|---|---|
| Тема | Make text output more generic |
| Дата | |
| Msg-id | GNELIHDDFBOCMGBFGEFOCEBICCAA.chriskl@familyhealth.com.au обсуждение исходный текст |
| Ответ на | Re: BETWEEN SYMMETRIC/ASYMMETRIC (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Make text output more generic
|
| Список | 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
В списке pgsql-hackers по дате отправления: