Re: Working oin pgAdmin2 - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Working oin pgAdmin2
Date
Msg-id FED2B709E3270E4B903EB0175A49BCB10475F1@dogbert.vale-housing.co.uk
Whole thread Raw
In response to Working oin pgAdmin2  (Jean-Michel POURE <jm.poure@freesurf.fr>)
Responses Re: Working oin pgAdmin2  (Jean-Michel POURE <jm.poure@freesurf.fr>)
List pgadmin-hackers

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm.poure@freesurf.fr]
> Sent: 24 February 2002 08:47
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: Working oin pgAdmin2
>
>
> Dear Dave,
>
> I got rid of manual SQL constructions in pgSchema->Views,
> just for testing
> and demonstration. Don't kill me, the job is more or less clean.

Hmmm.

> This demonstrates we could easily "mask" all SQL in pgSchema->Tables,
> Triggers, etc... And it could be possible to do the same in
> pgAdmin2. This
> makes it easy for developpers as they do not have to care for
> SQL. And this
> is the beauty of the code to mask SQL.

If a developer working on pgSchema cannot code the required SQL, then this
is *not* the project for him to be hacking. That's like a cowboy who can't
use a lassoo...

> Ultimately, this will allow an ***easy*** implementation of
> abstraction
> layers to query MySQL, Oracle and MS SQL Server from pgAdmin2.

I am not interested in implementing this., at least nothing more than can be
achieved via the ODBC API alone.

> This is not for now are there are more important
> projects (ALTER TABLE,
> Cygwin installer) going on.

Yes.

Regards, Dave.

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Schema unique stamp (OID, MD5?)
Next
From: Jean-Michel POURE
Date:
Subject: Re: Escaping quotes and double-quotes problem