From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'jm(dot)poure(at)freesurf(dot)fr'" <jm(dot)poure(at)freesurf(dot)fr> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Working oin pgAdmin2 |
Date: | 2002-02-24 20:19:24 |
Message-ID: | FED2B709E3270E4B903EB0175A49BCB10475F1@dogbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr]
> Sent: 24 February 2002 08:47
> To: Dave Page
> Cc: pgadmin-hackers(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2002-02-24 20:59:55 | Re: Escaping quotes and double-quotes problem |
Previous Message | Dave Page | 2002-02-24 20:14:13 | Re: Schema unique stamp (OID, MD5?) |