Michael J. Pawlowsky wrote:
Why not create a unique constraint with the userid, day (without time) and post content.
Is it going in a DB?
Index on text columns does not seem very efficient, IMHO.
If he wants to avoid multiple inserts, the random unique ID is enough.
--
PHP General Mailing Lis
How about saving a timestamp when the user posts a message and when he posts
another message check whether the user already posted a message in the past,
let's say, minute. I saw this used in a lot of forums...
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.
Why not create a unique constraint with the userid, day (without time) and post
content.
Is it going in a DB?
Mike
*** REPLY SEPARATOR ***
On 04/01/2003 at 3:26 AM OrangeHairedBoy wrote:
>Hi all,
>
>It seems that there might be some basic solution on this that I never
>receiv
Actually, there is a different solution to this aswell. One that is used
by phpBB and XMB, and maybe some others aswell.
Basicly, it's an anti-flood system. It works like this:
- You are a member and logged in
You post, and the post gets inserted into the database, and with it,
also the time o
I did searches on this one...I'm using NNTP so it's nice...unfortunatly, no
one had quite the same problem.
I had thought about the random value already (see paragraph about unique
visit id), but it just seems like so much to keep track of...
After asking on other board on the same topic, one the
on 04/01/03 7:26 PM, OrangeHairedBoy ([EMAIL PROTECTED]) wrote:
> Hi all,
>
> It seems that there might be some basic solution on this that I never
> received a memo on...
it's been mentioned MANY times on the list in the last week :)
> Basically, I'm looking for a way to avoid repeat posts. I
6 matches
Mail list logo
