Message-ID: <003701c0adfc$b905c1e0$1001a8c0@archonet.com>
From: "Richard Huxton" <dev@archonet.com>
To: "Roberto Mello" <rmello@cc.usu.edu>
Cc: <pgsql-docs@postgresql.org>
References: <20010315154535.B15441@cc.usu.edu>
	<20010316.215800@client.archonet.com>
	<20010316012320.A18007@cc.usu.edu>
Subject: Re: Re: [SQL] Contribute to the PL/pgSQL CookBook !!
Date: Fri, 16 Mar 2001 09:37:28 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

From: "Roberto Mello" <rmello@cc.usu.edu>

> On Fri, Mar 16, 2001 at 12:21:58AM +0000, Richard H wrote:
> >
>
> > You do realise you've built something that will grow to take over your
> > life and possibly the rest of the world?
>
> I hope we can get lots and lots of recipes. It'd be a great resource.
> Python has something of the sorts (association of O'Reilly and Active
> State if I am not mistaken).

No reason why you shouldn't end up with a library of useful chunks like CPAN
(well ish) - there are a host of standard templates and routines that people
don't need to keep re-inventing: international phone number formats,
email/URL format validation, standard contact templates...

> > If I can suggest some early enhancements (well, it's been running for
> > several hours now :-)
> >
> > 1. People will want to change their entries - take their email and send
> > them a password so they can edit it later.
>
> I thought about that, but my thinking was that if people had to
> register a login/password first, that might stop some people from
> cnotributing.
> What do others think? Allow for editing or not?

I was thinking about another slot for email and if they fill it in, you
generate a random password and email it to them automatically. They only
need to login next time, when they want to edit an existing entry.

You could store the email/password pairs in Access or MySQL or something ;-)

- Richard Huxton