[KLUG Members] database programming question

[Bruce Smith]

> > > If we could install MySQL on the KLUG server, I'd be happy to do a class
> > > on doing HTML forms with PHP and a MySQL backend.
> > 
> > I think that would be a good presentation!
> 
> I'd be happy to do it.

Cool.

> > But why does MySQL need to be on the KLUG server for this to happen?
> > I mean, the KLUG server is physically 30+ miles from the Chamber,
> > so why the KLUG server?  Why not some other server of yours on the
> > internet that already has MySQL installed?  What's the advantage of
> > the KLUG server?
> 
> Well, the best reason to put it on the KLUG server is they can begin to
> use forms more effectively on their site.  

Ah, so you're talking about writing something useful, not just making a
presentation.

> Seems rather Luddite to be
> passing paper forms around on Tuesday nights with vocal warnings to
> "Make sure to PRINT."

Yes it does!

> The second reason is it can be better used as a repository.  I can
> demonstrate on one of my servers but it is very valuable to leave
> examples available on the web so people can view them later when they
> need them.  My servers don't have any adequate place to put them because
> I'm always changing things (Even now, I don't know exactly where I put
> previous demonstrations.)   Everybody can remember the KLUG website and
> putting it there means it will remain available.  To have -working-
> demonstrations we need to have MySQL available on the server.
> 
> I guess the third reason is more subjective.  I'd bet that once MySQL is
> running, the website will have more input from its contributors.  I feel
> almost sheepish in noting that the lack of MySQL may have contributed to
> the lack of interactivity on the site.  MySQL's ease of use means people
> actually get brave enough to do things.  Hey, I'll even volunteer to do
> the first membership sign-up form.

I'm sure it's technically possible to add MySQL to the KLUG server, but
there are some concerns.

First the KLUG server is already running Postgresql.  I wouldn't doubt
that MySQL would run at the same time, except the KLUG server is old,
slow, and has limited memory.

Second, the KLUG server already has a lot of information stored in
Postgresql.  All the meeting/presenter info, supporting member info,
library info, and probably more.  It would seem like there would be an
advantage of keeping everything all in the same database for ease of
retrieval and use.

Third, the OpenGroupware server is using Postgresql, which we're talking
about integrating with the web server.

I'm sure either Postgresql and MySQL would do the job on the KLUG server
equally well, BUT is it worth the effort convert everything from PG to
MySQL?  What would that gain us?  (other than your subjective reason)

Also, can you explain why the advantages of LAMP over using PG?  Is PHP
easier?  The "select" statements are basically the same, aren't they? 
What is else is the difference other than changing the PHP calls from 
pg-connect/pg-select to mysql-connect/mysql-select? (or whatever)

 - BS