I was able to connect to a different database after I got the error.
However, now I could not get PgAdmin to crash.
After the first error, I connected to a different database with no problem.
Then I ran the query again, and got a slightly different error. Subsequent
runs of the query got the same
I'll check this.
I was running the test as if you had meant the latter, so I attempted to
disconnect from one of the databases to attempt to answer the former
question.
I was running the SQL test in two databases. When I went to disconnect from
one of the databases, the browser asked me if I want
The former.
On Monday, July 26, 2010, Michael Shapiro wrote:
> What do you mean: Can I select a different database after I get the error; or
> do I get the error using a different database?
>
>
> On Mon, Jul 26, 2010 at 2:05 PM, Dave Page wrote:
> On Mon, Jul 26, 2010 at 8:03 PM, Michael Shapir
What do you mean: Can I select a different database after I get the error;
or do I get the error using a different database?
On Mon, Jul 26, 2010 at 2:05 PM, Dave Page wrote:
> On Mon, Jul 26, 2010 at 8:03 PM, Michael Shapiro
> wrote:
> > What happens is that the first time it does give an err
On Mon, Jul 26, 2010 at 8:03 PM, Michael Shapiro wrote:
> What happens is that the first time it does give an error. But the editor is
> not useable. If I rerun the query a couple times, it can crash.
I tried running the query a bunch of times. It errored, but didn't crash.
Can you select a diff
What happens is that the first time it does give an error. But the editor is
not useable. If I rerun the query a couple times, it can crash.
On Mon, Jul 26, 2010 at 1:58 PM, Dave Page wrote:
> On Mon, Jul 26, 2010 at 5:41 PM, Michael Shapiro
> wrote:
> > I tested 1/12 beta. It has exactly the
On Mon, Jul 26, 2010 at 5:41 PM, Michael Shapiro wrote:
> I tested 1/12 beta. It has exactly the same problem. When the SQL editor
> loses the connection, rerunning the query causes PgAdmin to crash.
I can't reproduce that - it errors cleanly for me (which is why I
didn't work on the Query Tool e
Le 26/07/2010 20:04, Michael Shapiro a écrit :
> The IIRC patch works.
> Any chance of the SQL editor getting such a patch?
>
Could be. But not for 1.12, as we are on beta. I added a ticket for this
(http://code.pgadmin.org/trac/ticket/216).
--
Guillaume
http://www.postgresql.fr
http://dalib
The IIRC patch works.
Any chance of the SQL editor getting such a patch?
On Mon, Jul 26, 2010 at 11:48 AM, Guillaume Lelarge
wrote:
> Le 26/07/2010 18:41, Michael Shapiro a écrit :
> > I tested 1/12 beta. It has exactly the same problem. When the SQL editor
> > loses the connection, rerunning the
Sorry one mistake, I copied the value by selecting the cell and using
ctrl-c, there is no right-click copy.
On Mon, Jul 26, 2010 at 12:36 PM, Jeff Adams wrote:
> pgAdmin v1.10.3
> Windows XP SP3
> PostgreSQL 8.4.4
>
> Any time I do a select that produces a really really long value,
> instead of s
Le 26/07/2010 18:41, Michael Shapiro a écrit :
> I tested 1/12 beta. It has exactly the same problem. When the SQL editor
> loses the connection, rerunning the query causes PgAdmin to crash.
>
The patch Dave applied for 1.12 is only for the browser IIRC. The SQL
editor would need another patch.
I tested 1/12 beta. It has exactly the same problem. When the SQL editor
loses the connection, rerunning the query causes PgAdmin to crash.
On Fri, Jul 23, 2010 at 4:03 PM, Guillaume Lelarge
wrote:
> Le 23/07/2010 22:57, Michael Shapiro a écrit :
> > The visualtour page seems to imply that this w
pgAdmin v1.10.3
Windows XP SP3
PostgreSQL 8.4.4
Any time I do a select that produces a really really long value,
instead of showing the value pgAdmin has a blank cell in the output.
The value is actually there if I right click and copy, then paste into
a text editor, just not displayed. The value
13 matches
Mail list logo
