Received: from flex.flex.ro (flex.flex.ro [193.230.255.2]) by hub.org (8.8.8/8.7.5) with ESMTP id FAA22037 for ; Wed, 25 Mar 1998 05:50:33 -0500 (EST) Received: from flex.flex.ro (localhost [127.0.0.1]) by flex.flex.ro (8.8.8/8.7.3) with SMTP id MAA00683; Wed, 25 Mar 1998 12:55:02 +0200 Sender: teo@flex.flex.ro Message-ID: <3518E286.C61F15C@flex.ro> Date: Wed, 25 Mar 1998 12:55:02 +0200 From: Constantin Teodorescu Organization: FLEX Consulting Braila X-Mailer: Mozilla 3.04Gold (X11; I; Linux 2.0.32 i586) MIME-Version: 1.0 To: The Hermit Hacker CC: Simon Shapiro , Andreas Klemm , pgsql-interfaces@postgreSQL.org, hasty@rah.star-gate.com Subject: Re: [INTERFACES] Re: pgaccess "exec" queries References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The Hermit Hacker wrote: > > On Tue, 24 Mar 1998, Simon Shapiro wrote: > > > That will not make pgaccess understand non-SELECt SQL, I am afraid. > It is good enough for now. PgAccess handles "action queries", but only the saved ones. Make a new action query, save it, and open it!!! After a warning window, it will "pg_exec it" not "pg_select" it! > > > Not sure if that is wise or not, considering that pgaccess has a > > > new version released *much* more often then PostgreSQL itself, as new > > > features are added to it... I will solve this problem soon. > Fine with me. Do you know why I can only SELECT from pgaccess query > subwindow? Lack of time :-( I will look over the code, one of these days > I do not, but I've CC'd this into the pgsql-interfaces list where the > author tends to hang out... No. Had some contracts to work on. I always keep on eye on pgsql-interfaces and reply when someone in trouble. Had no time to develop further PgAccess (for the moment). -- Constantin Teodorescu FLEX Consulting Braila, ROMANIA