Thread: [bug] Execute pgScript Returns Error Without Executing The Query
I could not find this version is supported but it looks like serious bug. When executing query an pgScript used together pgScript returns an invalid error which it returned before. Version: pgadmin3 1.12.3-1 Platform: Linux 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux PostgreSQL Server Version: PostgreSQL 9.1.2 on i686-pc-linux-gnu, compiled by gcc (Debian 4.6.1-15) 4.6.1, 32-bit How to reproduce: * Open an SQL window * Execute pgScript: Select true from ATable * Execute query: Create table ATable (id int); * Execute pgScript: Select true from ATable [1] http://archives.postgresql.org/pgadmin-hackers/2009-03/msg00040.php
On Thu, 2012-01-26 at 12:41 +0200, Emre Hasegeli wrote: > I could not find this version is supported but it looks like serious bug. > When executing query an pgScript used together pgScript returns an invalid > error which it returned before. > > Version: pgadmin3 1.12.3-1 > You do know that 1.12 is obsolete, right? if ever we had to fix an issue, it would be on 1.14, and not 1.12. > Platform: Linux 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC > 2011 x86_64 x86_64 x86_64 GNU/Linux > > PostgreSQL Server Version: PostgreSQL 9.1.2 on i686-pc-linux-gnu, compiled > by gcc (Debian 4.6.1-15) 4.6.1, 32-bit > > How to reproduce: > > * Open an SQL window > * Execute pgScript: Select true from ATable > * Execute query: Create table ATable (id int); > * Execute pgScript: Select true from ATable > Works for me. > [1] http://archives.postgresql.org/pgadmin-hackers/2009-03/msg00040.php > What does this link have anything to do with your issue? -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com PostgreSQL Sessions #3: http://www.postgresql-sessions.org
On Thu, 26 Jan 2012 23:18:29 +0200, Guillaume Lelarge <guillaume@lelarge.info> wrote: > You do know that 1.12 is obsolete, right? if ever we had to fix an > issue, it would be on 1.14, and not 1.12. No problem. I thought it could be serious even it effects only previous version. > Works for me. Works on 1.14 or 1.12? If it is fixed on 1.14 do you know what was the problem? Does pgAdmin caches queries executed as pgScript. >> [1] http://archives.postgresql.org/pgadmin-hackers/2009-03/msg00040.php >> > > What does this link have anything to do with your issue? I searched the mailing list. That thread looks like related to me at first. Then I gave up to mention but forgot to remove the link.
On Fri, 2012-01-27 at 11:05 +0200, Emre Hasegeli wrote: > On Thu, 26 Jan 2012 23:18:29 +0200, Guillaume Lelarge > <guillaume@lelarge.info> wrote: > > > You do know that 1.12 is obsolete, right? if ever we had to fix an > > issue, it would be on 1.14, and not 1.12. > > No problem. I thought it could be serious even it effects only previous > version. > Actually, I don't even know your issue. All I see in your previous is three queries, and they all work for me. > > Works for me. > > Works on 1.14 or 1.12? If it is fixed on 1.14 do you know what was the > problem? 1.14. And to kown if it was fixed in 1.14, I would first have to understand what your issue is. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com PostgreSQL Sessions #3: http://www.postgresql-sessions.org
On Fri, 27 Jan 2012 12:32:45 +0200, Guillaume Lelarge <guillaume@lelarge.info> wrote: > On Fri, 2012-01-27 at 11:05 +0200, Emre Hasegeli wrote: >> On Thu, 26 Jan 2012 23:18:29 +0200, Guillaume Lelarge >> <guillaume@lelarge.info> wrote: >> >> > You do know that 1.12 is obsolete, right? if ever we had to fix an >> > issue, it would be on 1.14, and not 1.12. >> >> No problem. I thought it could be serious even it effects only previous >> version. >> > > Actually, I don't even know your issue. All I see in your previous is > three queries, and they all work for me. I should have include outputs of the queries: > On Thu, 2012-01-26 at 12:41 +0200, Emre Hasegeli wrote: >> How to reproduce: >> >> * Open an SQL window >> * Execute pgScript: Select true from ATable [WARNING ] Select true from ATable ERROR: relation "atable" does not exist LINE 1: Select true fromATable >> * Execute query: Create table ATable (id int) >> * Execute pgScript: Select true from ATable [WARNING ] Select true from ATable ERROR: relation "atable" does not exist LINE 1: Select true fromATable
On Fri, 2012-01-27 at 14:09 +0200, Emre Hasegeli wrote: > On Fri, 27 Jan 2012 12:32:45 +0200, Guillaume Lelarge > <guillaume@lelarge.info> wrote: > > > On Fri, 2012-01-27 at 11:05 +0200, Emre Hasegeli wrote: > >> On Thu, 26 Jan 2012 23:18:29 +0200, Guillaume Lelarge > >> <guillaume@lelarge.info> wrote: > >> > >> > You do know that 1.12 is obsolete, right? if ever we had to fix an > >> > issue, it would be on 1.14, and not 1.12. > >> > >> No problem. I thought it could be serious even it effects only previous > >> version. > >> > > > > Actually, I don't even know your issue. All I see in your previous is > > three queries, and they all work for me. > > I should have include outputs of the queries: > > > On Thu, 2012-01-26 at 12:41 +0200, Emre Hasegeli wrote: > > >> How to reproduce: > >> > >> * Open an SQL window > >> * Execute pgScript: Select true from ATable > > [WARNING ] Select true from ATable > ERROR: relation "atable" does not exist > LINE 1: Select true from ATable > > >> * Execute query: Create table ATable (id int) > >> * Execute pgScript: Select true from ATable > > [WARNING ] Select true from ATable > ERROR: relation "atable" does not exist > LINE 1: Select true from ATable > I tried 1.15, 1.14, and 1.12. They all work for me. First query, launched with pgScript, gave me an error because the table doesn't exist. Second query creates the table. Third query, launched with pgScript, just works. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com PostgreSQL Sessions #3: http://www.postgresql-sessions.org