Re: GUITools update

From: John DeSoi <desoi(at)pgedit(dot)com>
To: Stephane Bortzmeyer <bortzmeyer(at)nic(dot)fr>
Cc: Brennan Stewart <brennan(at)ideahamster(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: GUITools update
Date: 2005-04-29 12:21:32
Message-ID: 388EE75E-B8A9-11D9-88DF-000A95B03262@pgedit.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general


On Apr 29, 2005, at 4:27 AM, Stephane Bortzmeyer wrote:

> * Freeness of the code (which is much more important than price:
> switching tools is *hard* because of the lack of standards, so a small
> price at the beginning can lock you for a long time).

It seems like this is a minimal issue with most PostgreSQL tools since
they are designed to work with a representation of the database.
Generally, SQL is the representation so there is no lock in.

It might be useful to distinguish "freeness of code" (which does have
other advantages) from "proprietary binary data storage". Offhand I
can't think of any GUI tool which stores important data in a
proprietary format.

John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Hannu Krosing 2005-04-29 12:29:32 Re: [pgsql-advocacy] Increased company involvement
Previous Message Alvar Freude 2005-04-29 10:03:22 Re: GUITools update

Browse pgsql-general by date

  From Date Subject
Next Message Ian Harding 2005-04-29 13:38:54 Re: GUITools update
Previous Message Relyea, Mike 2005-04-29 12:18:33 Re: Postgresql and VBA vs Python