Existing users, 
 Navicat for PostgreSQL - 8.1.4Manage and develop for PostgreSQL. |
|
||||||||||||||||
|
|||||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
Multi-Document Model a winner 
- Version: 6.1.5, 4/6/2006 05:15PM PST
(1 of 1 users found this comment useful)
McClie
Despite the noted problems with not null columns and schemas, this is the best postgres gui I have tried for one simple reason: the multi-document model. When you click in the main window to do anything it opens a new window that is part of the same running instance. This means that you can use expose [F10] to view the open windows side by side, which is very helpful for a relational database set-up (i.e., when most columns are integers referring to entries in other tables). To compare free products you can use expose for Aqua Data Studio by using its Edit Table option, but there is no equivalent Edit Views option despite the fact that in many of ADS's supported database engines views are partially updatable. In Bigger SQL and PGnJ you can open a new connection, but in expose terms that is a separate instance and so can only be viewed by F9, where the windows tend to be too small to be much use.
The one thing holding me back from purchasing Navicat is its upgrade policy. It is free upgrades for minor revisions. As the Windows versions are at 7 and the OSX at 6 there is the danger of buying now and finding that the OSX bugs are fixed in a version for which you have to pay again. A license covering a major upgrade in the first 12 months would be better. This is particularly a problem in a product that is clearly a port from MySQL Navicat (e.g., you can only create rules in design table, when rules are the way to make a view updatable.)
The one thing holding me back from purchasing Navicat is its upgrade policy. It is free upgrades for minor revisions. As the Windows versions are at 7 and the OSX at 6 there is the danger of buying now and finding that the OSX bugs are fixed in a version for which you have to pay again. A license covering a major upgrade in the first 12 months would be better. This is particularly a problem in a product that is clearly a port from MySQL Navicat (e.g., you can only create rules in design table, when rules are the way to make a view updatable.)
Problem with not null columns - Version: 6.1.4, 3/17/2006 02:28AM PST
(2 of 2 users found this comment useful)
McClie
When adding a record and leaving it blank, on commit Navicat enters a null value, which is obviously a problem with non-null columns.
Most Recent Replies: View All 1 Replies
- Navicat's approach is correct, but ...
Namely, it's export procedures skip the export of sequences.
I have alerted their tech support, but response has been lethargic at best.
It also tends to crash on exit depending on which view you are in when you attempt to exit the application.
The user interface could do with some cleaning up, additionally the application does not have the look and feel of a native OSX app.
Considering the price - the support and quality is sub-standard.