From: | greg(at)turnstep(dot)com |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Suggestion for the postgresql.org survey |
Date: | 2003-02-26 14:44:08 |
Message-ID: | cadec5e9de7ae78a350954f6f9cededc@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In another thread ("7.4?") <20030226110156(dot)4FD8E4180F(at)mailer(dot)elma(dot)fr>,
someone wrote:
> ... looking the survey of Postgres.org web site :
> http://www.postgresql.org/survey.php?View=1&SurveyID=9
I would receommend taking the results of these polls with a large grain
of salt. I just reloaded my browser three times and watched the totals
change. Could we add a way to limit the ballot stuffing? I realize that
no method is perfect, but a simple cookie plus an IP restriction (with
timeout) should help immensely and not be too hard to implement.
Thanks,
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200302260934
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+XNGovJuQZxSWSsgRAj0cAJ4quXTKrH2ly1QDQ8WnRhQEGducCACfQw0D
jKJkdilJ07Hvp017ARPLUs0=
=CEfq
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Mick van der Most van Spijk | 2003-02-26 14:50:12 | Dynamically create scheme |
Previous Message | Patrik Kudo | 2003-02-26 14:30:05 | index usage (and foreign keys/triggers) |