This makes sense. I guess for now, however, we just continue the
development of the Graphical Editor in the standard way and worry about
dll-ing it later on.
Tim
>Not a good idea. Security is the job of the DBMS - anything we can do with
>pgAdmin could be overidden by a registry savvy user any
> -Original Message-
> From: Tim Finch [mailto:[EMAIL PROTECTED]]
> Sent: 03 April 2002 09:48
> To: Dave Page
> Cc: [EMAIL PROTECTED]; G. A. Reina
> Subject: Re: [pgadmin-support] SQL query editor
>
>
> At 07:21 30/03/2002 +, Dave Page wrote:
> &g
the pgAdminII, then surely a better approach is to have security in
pgAdminII that states what operators of pgAdminII can do (you can create
Dbs, edit them, create SQL etc. etc.)...?
Tim.
>_Original message ____
>Subject:[pgadmin-support] SQL query editor
>Sen
No, it doesn't I'm afraid. It's possible that it could be modularised and seperated
though, and it's a pretty good idea, so if I get a chance I'll look into it.
Regards, Dave.
_Original message ____
Subject: [pgadmin-support] SQL query ed
Does the SQL query editor on pgAdmin II come
as a separate program? I'd like to have a way on MS Windows for my
non-administrative users to perform SQL queries easily. I'm currently using
Interactive PgSQL, but it doesn't seem to be supported any more and there are
some bugs with executing q
