Re: BUG #8611: ECPG: unclosed comment "/*"

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, alexsav23(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8611: ECPG: unclosed comment "/*"
Date: 2013-11-25 02:53:29
Message-ID: 20131125025329.GC17272@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael, Tom,

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Michael Meskes <meskes(at)postgresql(dot)org> writes:
> > Well, I think we can in ecpg as ecpg knows whether it's parsing C code or SQL
> > code.

I tend to agree with Tom here but I feel like I'm missing something-
will this only make things "work" which would fail previously..? We
certainly don't want to risk breaking things for existing users, but
perhaps it's not possible to have existing code which works and this is
only 'loosening' of what we accept.

Thanks,

Stephen

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ronan Dunklau 2013-11-25 06:56:21 Re: Server may segfault when using slices on int2vector
Previous Message Pavel Stehule 2013-11-24 19:28:14 Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist