Skip site navigation (1) Skip section navigation (2)

Re: Patch for pgScript

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Mickael Deloison <mdeloison(at)gmail(dot)com>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Patch for pgScript
Date: 2009-01-21 12:39:38
Message-ID: 4977178A.3010606@hagander.net (view raw or flat)
Thread:
Lists: pgadmin-hackers
Hi!

Sorry for the delay in reviewing.

Does using "[PGSWARNG]" really make sense? It saves only *two*
characters over the much more readanle "[PGSWARNING]"


//Magnus

Mickael Deloison wrote:
> Hi pgadmin hackers,
> 
> First, let me wish you a very happy new year 2009.
> 
> Then, here is a patch for the pgScript part of pgAdmin:
> Features:
> - Use of pgAdmin UI to highlight the line where an error occurred
> (frmQuery, pgsDriver, pgsThread, pgsApplication, pgsStmtList)
> - Possibility to execute only one part of the script by selecting it (frmQuery)
> - Changed output style (exceptions/*, expressions/pgsExecute,
> statements/pgsStmtList)
> - Improved the script for integration tests: it does not print the
> executed queries anymore because the output was too messy
> (xtra/pgscript/file/test/execute.sh)
> Bugs:
> - Fixed print statement which caused a lock in case an exception was
> thrown (statement/pgsPrintStmt)
> 
> Best regards,
> Mickael
> 
> 
> ------------------------------------------------------------------------
> 
> 


In response to

Responses

pgadmin-hackers by date

Next:From: Dave PageDate: 2009-01-21 13:38:04
Subject: Re: Patch for pgScript
Previous:From: Quan ZongliangDate: 2009-01-21 10:54:45
Subject: Import: function report

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group