pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: David Bear <David.Bear@asu.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: front end application
Date: Wed, 12 Oct 2005 14:22:39 -0500
Message-ID: <20051012192239.GF23883@pervasive.com> (raw)
In-Reply-To: <20051012171102.GC25743@asu.edu>
References: <20051012171102.GC25743@asu.edu>

I've heard good things about using Access as a front-end to PostgreSQL.
Haven't done it myself, though.

Have you considered using SSL to secure your communications? There are
programs out there for windows that make it pretty easy to tunnel a
connection via SSL, so this would probably be better than using SSH.
Then you can just let PostgreSQL handle user authentication.

On Wed, Oct 12, 2005 at 10:11:02AM -0700, David Bear wrote:
> I've been playing with postgresql for a while now. I'm curious how
> others develop front ends for pg. I have looked at using pgaccess, and
> ReKall. Both seem pretty good. 
> 
> I've also been playing with MS Access
> and using the pgodbc drivers. I am using kerberized ssh access to the
> linux box running pg8. If I used the odbc driver then I need to tunnel
> that to pg -- and then I have to put up with the typical windows user
> not reading the simple instructions to click on an icon to log into a
> system -- and then I have to worry about what kind of shell to give to
> a user if they are only using pg.
> 
> On the other hand, if I develop in pgaccess or ReKall then I have them
> shell into the linux box and actually make 'that' there shell -- but
> then I have to tunnel X.
> 
> It doesn't seem like nirvana -- and it is not as 'seamless' as using
> the product from Redmond that shall not be named.
> 
> So, I am very interested in what others are using to build a good ui
> for a pg application. Any comments?
> 
> -- 
> David Bear
> phone: 	480-965-8257
> fax: 	480-965-9189
> College of Public Programs/ASU
> Wilson Hall 232
> Tempe, AZ 85287-0803
>  "Beware the IP portfolio, everyone will be suspect of trespassing"
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
> 

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (3+ messages)  latest in thread

Message-ID: <20051012192239.GF23883@pervasive.com>
Permalink:  ../20051012192239.GF23883@pervasive.com/
Also on:    postgresql.org/message-id/20051012192239.GF23883@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, David.Bear@asu.edu
  Subject: Re: front end application
  In-Reply-To: <20051012192239.GF23883@pervasive.com>
  References: <20051012171102.GC25743@asu.edu> <20051012192239.GF23883@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox