Re: pgAdmin 1.3.76

Thanks Dave! I checked my following previously reported errors against the new current version:

* SELECT MAX(`OID_key`) AS RECCOUNT FROM `OID_root`CREATE SEQUENCE "OID_root_OID_key_key" START 356
* Notice the back ticks (`) around OID_key. These promptly cause an error (illegal syntax I think it was?)
* which causes an abort and a rollback of the migration.

This bug magically disappeared with this version

* In version the new version, when I connect to my database, it doesn't show me any of my tables with the
* new version. I believe that this may have something to do with the fact that my table names contain
* capital letters....

This was never a bug... (darn blind users reporting bugs that didn't really exist)... they were hiding under the schema... : )

*Database Migration Wizard Plugin for pgAdmin II 1.2.0 does not properly handle empty strings from an MS
* Access Database.
* When processing a column with a data type of Text, which is required but allows 0 length fields, and
* it encounters an empty string "", instead of passing the value as "", it just leaves out that column,
* which causes the database to try to set it to NULL, but NULL is not a legal value for the column.

Fixed. Works perfectly for me now.

* The download for pgAdminII v1.3.60 (Alpha release) on
* http://pgadmin.postgresql.org/downloads/ is > broken.
*
* The zip
* file gives a crc error when you try to unzip it.

This turns out to be some sort of odd error with Mozilla, however, both version 1.2 and 1.3.76 work fine when downloaded with mozila. I reported it to Mozilla, and while it was not previously unheard of, most people reported back wfm (works for me)

*****************************
Daniel C. Armbrust
Medical Informatics Research
Information Services
Mayo Clinic Rochester
*****************************

-----Original Message-----
From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
Sent: Monday, August 19, 2002 9:02 AM
To: pgadmin-hackers(at)postgresql(dot)org; pgadmin-support(at)postgresql(dot)org
Cc: pgsql-announce(at)postgresql(dot)org
Subject: pgAdmin 1.3.76

I'm pleased to announce the release of pgAdmin II 1.3.76. This is the
second release from the 1.3 development code.

pgAdmin II is an open source PostgreSQL database design and management
tool for Windows platforms. Further information and downloads can be
found at http://www.pgadmin.org/.

This release includes extensive changes to support schemas in the
upcoming 7.3 release of PostgreSQL. Testing on both current and
development versions of PostgreSQL is encouraged - any bug reports
should be sent to the support mailing list:
pgadmin-support(at)postgresql(dot)org(dot)

Changes in this release include:

- Fixed a bug that attempted to access inaccessible databases when
clicked on in the treeview.
- Use doubles instead of longs to cope with very large OIDs.
- Fixed a bug that caused an error if the pgAdmin window was too small
when the listview was populated.
- Don't class 'public' as a system schema.
- Don't throw an error when changing Not Null/Primary Key on a new
column in an existing table.
- Don't allow (attempted) alteration of certain column attributes in
PostgreSQL 7.2.
- Fixed some errors in the function editor.
- Raise errors properly from pgSchema.
- Only quote identifiers in datagrid update queries when required.
- Allow use of numeric identifiers.
- Fixed a bug that prevented renaming columns.
- Fixed an error that occured when clicking on the Relationships node
under a Foreign Key.
- Fixed a bug that prevented updating of Sequence values.
- Display object counts in the treeview immediately now we know them in
advance.
- Handle dates/time formats supported by Windows, not just those
supported by PostgreSQL (particuarly those that use . seperators)
- Allow use of F5 to execute SQL queries (Andy Kelk).
- If SQL is highlighted in the SQL textbox, execute only that, not the
whole query (Andy Kelk).
- Fixed a bug where an SQL file got overwritten if the user clicked
'Cancel'.
- Added DROP COLUMN support (Wahoo!).
- Don't display ON UPDATE/ON DELETE clauses in Foreign Keys if
unspecified.
- Fixed broken error handling in pgSchema.

The Migration Wizard (distributed seperately under GPL) has also been
updated:

- Correctly clear CREATE SEQUENCE sql. [John McCawley]
- Check the Migration type in a more sensible way. [John McCawley]
- Insert empty values correctly to avoid errors by not inserting into
NOT NULL columns.

Regards, Dave.