pgAdmin III v1.8.2 released
Posted on 2008-02-03
The pgAdmin Development Team are pleased to announce the release of pgAdmin 1.8.2, the Open Source graphical PostgreSQL administration tool for Windows, Linux, FreeBSD, Mac OS X and Solaris, now available for download in source and a variety of binary formats from:
v1.8.2 is primarily a bug fix release, including the following changes:
- Size of the column label of SQLGrid was made variable.
- Prevent a crash when viewing databases with % in the name.
- Don't try to force new databases into a specific tablespace as this will error is non-superusers default to pg_default.
- Correct the SQL generation for EDB inline triggers.
- Generate function signatures correctly if the first parameters are OUT only.
- Remove the confusing and near-useless sequence combo box from the column dialog per discussion on support list.
- Fix the WITH ADMIN membership option when creating roles.
- Refresh Views correctly on EnterpriseDB.
- Fix the privilege editor on the Language dialogue, per Bborie Park.
- Correctly identify the schema of trigger functions that are in system catalogs as can be the case with integrated full text search.
- Warn the user if a file cannot be saved in the default encoding.
- Undecorated out-param types must be included in EDB-SPL function signatures when altering comments or privileges or dropping functions or procedures.
- Ensure enums are offered as datatypes for columns.
- Fix column dialogue to allow proper modification of array columns per Erwin.
- Newer build of EnterpriseDB consistently strip trailing semi-colons from package headers and bodies. Update reverse engineering allow for this.
- Ensure the properties dialogues will work sanely with objects named " " (!).
- EDB-SPL functions require NULL to be passed in out-params when debugging.
- Ensure that EDB-SPL trigger DDL code is appropriately formatted on newer builds of EnterpriseDB.
- Ensure the password and confirmed password always match when adding or editing roles or users.
pgAdmin Project Lead
This post has been migrated from a previous version of the PostgreSQL
website. We apologise for any formatting issues caused by the migration.