Skip site navigation (1) Skip section navigation (2)

Working oin pgAdmin2

From: Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Working oin pgAdmin2
Date: 2002-02-24 08:46:59
Message-ID: 200202240847.g1O8kxFP000356@www1.translationforge (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
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.

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.

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

Last week-end, I had a deep look at libgda. This is a quite simpleabstraction 
layer written in plain C. It does have the power or a C++ object oriented 
abstractionlayer. But it has nice things like abstract types and type 
conversion (I guess).

We could well implement "database providers" in pgSchema to offer basic 
access to other database schemas. This could well be in read-only in a first 
time. This is not for now are there are more important projects (ALTER TABLE, 
Cygwin installer) going on.

But if we move SQL queries ***out*** of pgAdmin2 and pgSchema->Tables, 
Triggers, etc.., this will be possible in a middle-term future. We need more 
abstraction from SQL...

What do you think?


pgadmin-hackers by date

Next:From: Dave PageDate: 2002-02-24 08:52:20
Subject: Re: Schema unique stamp (OID, MD5?)
Previous:From: Jean-Michel POUREDate: 2002-02-23 21:42:28
Subject: Re: Schema unique stamp (OID, MD5?)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group