Why pgEdit?

Editors are for application development

There are many PostgreSQL development and administration tools available, and some are free. But pgEdit is the first editor optimized solely for PostgreSQL development. The typical PostgreSQL tool gives a big tree view of databases, schemas, tables, functions and so on (pgEdit will eventually have one too). This is fine for administration or simple development tasks, but gets in the way of developing complex database applications. The key issue is that an editor provides locality - you can group related tables, functions, triggers, and other database objects together in a file. As with other software development, you can build version controlled files of logically related objects rather than trying to work from a from a big tree view of objects listed by type and in alphabetical order.

All PostgreSQL, all the time

Some tools work with many different databases via interfaces like ODBC or JDBC. This is great if you regularly use many different databases, but it tends to make the application support only the lowest common feature set which applies to all of them. pgEdit aims to be a great application for PostgreSQL rather than being marginal or overly complex in supporting many different databases. PostgreSQL is powerful, free, and runs on every major operating system. Why use anything else?

Programmers are picky

We all have certain programming actions and sequences that are forever imprinted in our DNA. Trying to change them causes immense pain and repeated mistakes. In this regard, pgEdit tries to be as flexible as possible. You can change the keyboard shortcut of almost every menu item or command. A future version of pgEdit will allow you to modify and create menus.

Syntax coloring saves time and reduces errors

PostgreSQL has more than 350 built-in keywords and data types. Using one of these as the name of a table or column can cause subtle problems that are difficult to identify. pgEdit syntax coloring lets you know immediately and unobtrusively when you have typed a keyword. Conversely, if you type the name of a built-in function or keyword and the color does not change, you are immediately aware of the error. This saves the time and trouble of executing the code, reading the error message, and then finding and fixing the error.

Complexity and incremental revelation

We all want software that is powerful and flexible yet easy to learn and use. This is a very difficult goal to achieve, especially for complex databases like PostgreSQL. pgEdit aspires to achieve this with the concept of incremental revelation - start with simplicity and provide more power and flexibility as needed. When you first start pgEdit, you see only a couple menus not found in a typical application. These menus provide the primary operations needed to get started with SQL editing and execution. But opening the command help window reveals there are about 300 commands available. You can execute any of these commands by name or assign keyboard shortcuts to the ones you want to use frequently.

Macs need love too

The Macintosh OS is a great platform for PostgreSQL - a very nice user interface with Unix underneath. But the choices for powerful PostgreSQL development tools are limited on the Macintosh platform. pgEdit aims to change this.

Resources: