[KLUG Members] database programming question

[Bruce Smith]

> > First off you're talking duplication of data.  There is already some
> > membership information in Postgresql (supporting member database). 
> > Do I need to explain why duplication of data is bad?
> 
> There is also data off-site in a groupware server.  Just to add some
> more fun. :)

And what database is that stored in?
(pretend I don't already know the answer :)

> > This is a volunteer organization.  No money (or other compensation) is
> > exchanged for services rendered.  Anyone who has been involved in a
> > volunteer organization knows how hard it is to get anything done.
> 
> Yep, and you need to get people to voluntarily agree!  See how much fun
> that can be? ... Actually with this group it tends to be a hoooot, one
> of the many reasons I've stuck around.  
> 
> Officers meetings are often like the spanish inquisition minus all the
> blood and pesky religion. :)

You should be the person recruiting new volunteers!  :-)

> > ... Why?
> 
> Well, I think the issue is testing.  It is easier to write a script for
> which you have a local db to test against, than one where you don't.

True, but people who volunteer to write some serious PHP code for KLUG
can get an account on the KLUG server, and can do there testing there.

Plus they can come to the officer's meetings to join in all that fun, as
you previously pointed out!  :-)

I won't even get into all the fun of the private officer's mailing list.
Especially when Bob says something stupid and I have to put him in his
place!!!  ;-)

> > Howabout if we spell it "odbc_query"?  (or whatever the ODBC call is)
> > Then you won't have to know which DB you're using.  :-)
> 
> I like it!

Always an option.

 - BS