Re: ecpg - GRANT bug
От | Lee Kindness |
---|---|
Тема | Re: ecpg - GRANT bug |
Дата | |
Msg-id | 15307.64910.421696.852199@elsick.csl.co.uk обсуждение исходный текст |
Ответ на | Re: ecpg - GRANT bug (Lee Kindness <lkindness@csl.co.uk>) |
Ответы |
Re: ecpg - GRANT bug
Re: ecpg - GRANT bug Re: ecpg - GRANT bug Re: ecpg - GRANT bug Re: ecpg - GRANT bug |
Список | pgsql-hackers |
Lee Kindness writes:> Patch below, it changes:> 1. A number of mmerror(ET_ERROR) to mmerror(ET_NOTICE), passing on> the (currently) unsupported options to the backend with warning.> 2. Standardises warning messages in such cases.> 3. Correctstypo in passing of 'CREATE FUNCTION/INOUT' parameter. And the patch below corrects a pet peeve I have with ecpg, all errors and warnings are output with a line number one less than reality... Lee. *** ./interfaces/ecpg/preproc/preproc.y.orig Tue Oct 16 10:19:27 2001 --- ./interfaces/ecpg/preproc/preproc.y Tue Oct 16 10:19:49 2001 *************** *** 36,49 **** switch(type) { case ET_NOTICE: ! fprintf(stderr, "%s:%d: WARNING: %s\n", input_filename, yylineno, error); break; case ET_ERROR: ! fprintf(stderr, "%s:%d: ERROR: %s\n", input_filename, yylineno, error); ret_value = PARSE_ERROR; break; case ET_FATAL: ! fprintf(stderr, "%s:%d: ERROR: %s\n", input_filename, yylineno, error); exit(PARSE_ERROR); } } --- 36,52 ---- switch(type) { case ET_NOTICE: ! fprintf(stderr, "%s:%d: WARNING: %s\n", input_filename, ! yylineno + 1, error); break; case ET_ERROR: ! fprintf(stderr, "%s:%d: ERROR: %s\n", input_filename, ! yylineno + 1, error); ret_value = PARSE_ERROR; break; case ET_FATAL: ! fprintf(stderr, "%s:%d: ERROR: %s\n", input_filename, ! yylineno + 1, error); exit(PARSE_ERROR); } }
В списке pgsql-hackers по дате отправления: