Make sure no query more than max size is stored...
in the historic file.
The issue was that, if pgAdmin was killed, the last query, whatever its size,
remained in the histoqueries file. I changed the behabiour so that it can't
happen anymore.
Old behaviour:
When query is launched
Save
Make sure no query more than max size is stored...
in the historic file.
The issue was that, if pgAdmin was killed, the last query, whatever its size,
remained in the histoqueries file. I changed the behabiour so that it can't
happen anymore.
Old behaviour:
When query is launched
Save
Two forgotten items on the roadmap.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin-www.git;a=commitdiff;h=f44ac950558a6ecb3a9fdf5226c61e4afcf5545d
Modified Files
--
development/roadmap.php |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
Hi
On Mon, Dec 27, 2010 at 2:32 AM, Jasmin Dizdarevic
jasmin.dizdare...@gmail.com wrote:
Hi,
we've just decided to use pgAgent in our company, so I set it up and
discovered that there is no email notification support on failures.
I've decided to add this functionality, but I have some
Update readme for VC++ 2008, DLL builds
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=efa5bd8e35a19bf95bbb6ca2a51a1dcd9391eb5b
Modified Files
--
xtra/wx-build/readme.txt |8
1 files changed, 4 insertions(+), 4
On Sun, Dec 26, 2010 at 1:34 PM, Hiroshi Saito z-sa...@guitar.ocn.ne.jp wrote:
I don't know Windows build enough to be sure, but are you sure you
changed your build to a dynamic one? I know I had issues with building
on Windows right after this change. It wasn't Dave's fault, but mine. I
