| From: | Michael Shapiro <mshapiro51(at)gmail(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, UNTERRAINER(dot)Guenther(at)leitwind(dot)com, PgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: feature request |
| Date: | 2012-03-08 14:20:02 |
| Message-ID: | CAGCvxeaAVADSXLm8wDAJuHtGyJPZ5XmDSaoZWgwxEfVuMLi-sQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
You're right. That complicates it.
On Thu, Mar 8, 2012 at 6:43 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Thu, Mar 8, 2012 at 12:26 PM, Michael Shapiro <mshapiro51(at)gmail(dot)com>
> wrote:
> > SInce postgres would require a semi-colon between stmts, you could use
> that
> > fact to determine where a stmt starts and where it ends (even for the
> case
> > when the last stmt doesn't have one)
>
> What if there's a semi colon in a comment, string, anonymous block or
> stored procedure? We need a parser to deal with that, not just a
> simple split on semi colons.
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | michel boekestein | 2012-03-08 16:27:26 | Re: Failed to write to history file |
| Previous Message | Guillaume Lelarge | 2012-03-08 13:18:00 | Re: feature request |