I haven't tried many of them, but I didn't like how they scribbled on
my database. Hopefully now they are creating/using their own either
database or at least schema for all their data.
On 4/29/05, John DeSoi <desoi@pgedit.com> wrote:
>
> 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
