Re: commenting sql code

Поиск
Список
Период
Сортировка
От joseph speigle
Тема Re: commenting sql code
Дата
Msg-id 20040220150025.GA19785@www.sirfsup.com
обсуждение исходный текст
Ответ на Re: commenting sql code  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-novice
hello tom and bruno,

Thanks for solving this issue for me.  Doing as you say \i and not \e correctly ignores comments.  All I wanted to do
BTWwas what it looks like: edit an sql file from the cwd in the buffer and run it as a script when I close the buffer
(Iwant to say vi buffer and "quit vi with :wq").  I hadn't tried loading the file with \i.  I also notice now that it
runscorrectly doing psql -d test < file_name.sql and correctly ignores the comments, but before I wasn't sure if
postgreshad special comment syntax!! 

On Fri, Feb 20, 2004 at 09:42:55AM -0500, Tom Lane wrote:
> Bruno LEVEQUE <bruno.leveque@net6d.com> writes:
> > In your example you must use \i and not \e
>
> On investigation, this is actually a bug in the way \e works --- when
> the file is read back into psql, it's effectively treated as a single
> line, and so the comment kills more than you'd expect.  I am amused to
> realize that the bug is fixed in CVS tip, as a completely unintended
> consequence of the flex rewrite I just did ...
>
> But I agree that \i not \e is the preferred way to invoke a SQL file
> that already exists.  I am not sure if that's what Joe was trying to
> do or not.
>
>             regards, tom lane
joe
--
speigle
www.sirfsup.com

В списке pgsql-novice по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: commenting sql code
Следующее
От: beyaNet Consultancy
Дата:
Сообщение: Binary retrieval - *Best practice* recommendations...