Haven't had enough time for my previous reply to make it back to me so I could
reply to it
If using SQL, you might be able to do row or table locking to get around any
race conditions.
"Rob Bloodgood" <[EMAIL PROTECTED]> wrote:
>> A really simple trick would be rather than to use a cookie,
"Rob Bloodgood" <[EMAIL PROTECTED]> wrote:
>> A really simple trick would be rather than to use a cookie, if
>> you are saving state to DB anyway. Set a flag in the DB and test
>> for its existence.
>>
>> sub handler{
>>
>> my $s = session->new();
>> $s->continue();
>>
>> my
On Thu, 17 May 2001, Rob Bloodgood wrote:
> So, like many of you, I've got a signup system in place for bringing on new
> customers.
>
> My signup script is reasonably straightforward. I use CGI::Validate to make
> my parameters pass muster (along with a little judicious JavaScript on the
> si
Hi Rob,
On Thu, 17 May 2001, Rob Bloodgood wrote:
> But it doesn't work. I still get duplicate accounts, and I'm at a loss
[snip]
> Suggestions?
As you're using Oracle, why not use a constraint?
73,
Ged.
Rob Bloodgood wrote:
>
> So, like many of you, I've got a signup system in place for bringing on new
> customers.
>
> My signup script is reasonably straightforward. I use CGI::Validate to make
> my parameters pass muster (along with a little judicious JavaScript on the
> signup form), Apache::
> A really simple trick would be rather than to use a cookie, if
> you are saving state to DB anyway. Set a flag in the DB and test
> for its existence.
>
> sub handler{
>
> my $s = session->new();
> $s->continue();
>
> my $flag = $s->get('flag');
> if($flag){
> #
Once your signup engine is ready to perform all database entries, have it
set and commit a flag in the session indicating that it is processing. Once
the signup process is complete, set a flag in the session indicating this as
well. You must now add two tests to your signup engine to avoid dupes
