Depending on what you plan to do, there are a couple of ways to approach
this problem.
First, I've got to say that I use PostgreSQL for quite a
while and haven't had any major problems with it yet. It is doing fine
with a over 2.1 Gig database on my Intranet.
I use PHP3 (www.php3.com) HTML preprocessor to access the database and it
does the job incredibly well. It was easy to set up and to program. The
only fallback is that I had to recompile the existing Apache with the
PHP3 module support. PHP3 itself is very flexible and saves a bunch of
time, in comparison to PERL programming (although I do that too).
Denis Voitenko
[EMAIL PROTECTED]
On Thu, 15 Apr 1999 [EMAIL PROTECTED] wrote:
>
>
> Thanks to all for the comments, but I must add that, for several reasons,
> I'm forced to use postgress. My question is about the experience "linking"
> this to Apache. As I commented I'm thinking in using C (due to the fact
> that part of the app is already coded in C with E/SQL). Any comments on
> this?
>
> Best Regards
> F. Marquez
>
>
> -====---====---====---====---====---====---====---====---====---====---====-
> to unsubscribe email "unsubscribe linux-admin" to [EMAIL PROTECTED]
> See the linux-admin FAQ: http://www.kalug.lug.net/linux-admin-FAQ/
>
-====---====---====---====---====---====---====---====---====---====---====-
to unsubscribe email "unsubscribe linux-admin" to [EMAIL PROTECTED]
See the linux-admin FAQ: http://www.kalug.lug.net/linux-admin-FAQ/
