Обсуждение: Since I can't seem to unsubscribe to this mailing list, I might as well report a bug...

When working in the SQL query window in pgAdmin, keeping it open for the whole day, I sometimes notice that it will
randomlytell me that I have a syntax error somewhere in it when I run it, without having changed anything. If I just
clicksomewhere else inside the window, such as placing the marker in the end of the query, and execute it again, it
willrun. So without any actual changes, it runs/doesn't run.
 

Is this known? Why does it happen? How can it be possible? And so on.

(No, I cannot reliably reproduce this. I don't even know when it happens. I just know it does happen, and has happened
formany versions of pgAdmin over the years.)
 

Whoa. That's actually quite scary since I had no idea about it. What if I had selected only the "DELETE FROM table"
from"DELETE FROM table WHERE id = 123"?! Now I have to worry about having done that (or something similar) in the past.
:/

On 2015-02-12 at 10:23 AM, "Robins Tharakan" <tharakan@gmail.com> wrote:
>
>On 12 February 2015 at 02:33, <hushthatbush@hushmail.com> wrote:
>
>> I sometimes notice that it will randomly tell me that I have a 
>syntax
>> error somewhere in it when I run it, without having changed 
>anything. If I
>> just click somewhere else inside the window, such as placing the 
>marker in
>> the end of the query, and execute it again, it will run.
>
>
>​
>​I have a good feeling that this is because the times when it 
>gives 'syntax
>error' either by mistake or unknown to you, the SQL query window 
>has
>something selected (by mouse / shift + arrow keys)​ and then (by 
>design)
>PgAdmin runs just that piece of text. In most cases the obvious 
>error would
>be Syntax Error since now its a partial SQL being sent off to the 
>PG
>database...  "if" this is happeneing, this is by-design and a 
>'feature'. In
>fact most common SQL query consoles (GUI) happen to work like this.
>​​
>--
>Robins Tharakan