HTML and DocBook output

If you need to produce documentation with SQL source code, pgEdit has several commands you might find useful. The Copy for HTML command copies the selected source text to the clipboard in HTML format. The HTML consists of a PRE element with SPAN elements to describe the syntax coloring. The CSS From Syntax Colors command can be used to copy a cascading style sheet (CSS) fragment to the clipboard with your current color settings. This allows you to modify the syntax coloring used in any HTML page by having them all refer to the same CSS file.

The Copy for DocBook command performs a similar function in creating a DocBook ProgramListing element with syntax coloring information on the clipboard. The XSL From Syntax Colors command puts the XSL style sheet information for the current color settings on the clipboard. This information, along with the CSS style information, allows DocBook to be used to produce syntax colored program listings for both HTML and PDF output.

Here is a short trigger function to illustrate the HTML output:

Resources:

Access control functions for PostgreSQL

PostgreSQL provides a number of access control options, but granting privileges en masse can be difficult. For example, the GRANT command requires that each table be explicitly listed in the statement. To overcome this, Andrew Hammond and Tim Goodaire created some SQL functions to simplify this and several other administration tasks related to access control.

Resources:

Request features for pgEdit

Using EXPLAIN in pgEdit

pgEdit has three commands to execute variations of PostgreSQL's EXPLAIN command. In PostgreSQL this command is used to provide execution plan information about the SQL statement. All three forms of the pgEdit command make it easy to use EXPLAIN for anything in your file without making modifications. The pgEdit Explain command simply executes the current SQL line containing the cursor with PostgreSQL's EXPLAIN keyword prepended to the statement. Similarly, the Explain Analyze command prepends EXPLAIN ANALYZE which actually executes the command giving actual rather than estimated statistics.

Resources:

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.

Resources:

pgEdit 1.0 Released

After several months of testing, feedback, and improvements, pgEdit 1.0 is now available. This version includes a free trial period through February 14, 2005. During this time all pgEdit features are available with no demonstration mode limitations.

pgEdit 1.0b6

One final pgEdit beta before the release of PostgreSQL 8.0. In addition to bug fixes and usability improvements, 1.0b6 includes the following new features:

Direct execution of SQL and psql commands without including them in the document. Commands can be executed at the bottom of the editor window with full completion support, command history navigation, and syntax coloring.

Support for copying syntax colored SQL with HTML and DocBook markup. This produces nice looking output for documentation and publishing. HTML and XSL style specifications are generated from your pgEdit syntax color preferences.

pgEdit 1.0b5

pgEdit 1.0b5 is now available. This version adds support for Windows NT 4.0 and Windows 2000. In addition to some minor bug fixes, this version includes some new editing features and another option for executing files with psql. The final version of pgEdit is expected shortly after PostgreSQL 8.0 is released.

pgEdit 1.0b4

The next beta version of pgEdit is available for evaluation. This version includes a new tab completion feature based on the implementation in psql. In addition, there are 14 other completion commands where you can request a specific type of completion (e.g. table, column, function). As with all pgEdit commands, the completion commands can be bound to any key sequence of your choosing.

pgEdit public beta for Windows and Macintosh

pgEdit version 1.0b3 is now available for both Macintosh and Windows. This is the first public beta; feel free to download and evaluate pgEdit. Send bug reports, requests, and any other feedback to the email address provided on the support page.

Pages

Subscribe to pgedit.com RSS