I've been having very good results using Enhydra (see http://www.enhydra.org, or
specifically for the open source version, http://enhydra.enhydra.org). This
uses JDBC.
Jim
--
David Link wrote:
>
> > > I'm playing around with Macromedia's Dreamweaver and ColdFusion which
> > > can use ODBC to connect to databases. (It can also use JDBC, OLE DB
> > > and
> > > has native support for Oracle and others -- not PG though :-)
> >
> > IMHO, Dreamweaver and Coldfusion leave a lot to be desired as real
> > production platforms. For playing around, they've OK.
>
> What I have found for Web application development with Database are the
> following solutions, in order of desirability:
>
> 1. Perl CGI programs using Perl:DBI for Database connectivity.
>
> This gives you lots of flexibility. And with Apache Perl Mod you no
> longer need to fork a new process for every client request.
>
> 2. Java Server Pages (JSP) using JDBC. It requires some Java Servlet
> Engine running along side Apache.
>
> This gives you lots of flexibility, although development is not as
> fast as perl development. One could start out with Perl CGI and migrate
> to JSPs as a project becomes more robust.
>
> 3. Macromedia's ColdFusion Server running along side Apache. It uses
> ODBC. It allows the use of ColdFusion Tags to extend HTML and allow SQL
> (among other things).
>
> This is about as effective as using PHP or ePerl.
>
> 4. Active Server Pages (ASP) by Microsoft. This requires the use of the
> IIS web server rather than Apache. ASPs can use Microsoft's ActiveX
> Document Object (ADO) model on top of Microsoft's OLE DB database
> connectivity which may rely on ODBC to connect to Databases that do not
> support M$'s OLE DB.
>
> Too proprietary.
>
> What are other people's opinions on this?
> What is www.postgresql.org developed on?
>
> Thanks -David
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
