From: | "Jonathan Villa" <jvilla(at)innovativesource(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: how to select |
Date: | 2005-07-29 19:48:41 |
Message-ID: | 48358.216.125.144.21.1122666521.squirrel@mail.innovativesource.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-Jonathan
<quote who="Jaime Casanova">
> On 7/29/05, Jonathan Villa <jvilla(at)innovativesource(dot)net> wrote:
>>
>> Ok, this is odd...
>>
>> I tried ending with a semicolon before, and received this error
>>
>> ERROR: parser: parse error at or near "select"
>>
>> I have to do it twice before I get it works...here's an example
>>
>> select project_name from project_group_list;
>> ERROR: parser: parse error at or near "select"
>> select project_name from project_group_list;
>> ...
>> ...
>> ...
>>
>> that's odd...
>>
>>
>
> that's because you type a select without a semicolon then you write
> one with the semicolon so the parser think both are only one command
> but refused to execute that bad formed sentence and give you the
> error... then you put another sentence and, of cuorse it executed...
>
> you just show us 2 sentences one before the error and one after...
>
> am i right?
>
> --
> Atentamente,
> Jaime Casanova
> (DBA: DataBase Aniquilator ;)
>
I feel about this small -> .
Of course it's the semicolon... I guess I'm just used to MySQL where I would get this
select user from table (hit enter)
->
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-07-29 19:49:54 | Re: [GENERAL] MySQL to PostgreSQL, was ENUM type |
Previous Message | Scott Marlowe | 2005-07-29 19:42:14 | Re: how to select |