perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "petersm" <pete...@venzia.com>
Subject Re: some children not returning newly-inserted data
Date Sun, 02 May 2004 13:35:12 GMT

Dave Boodman wrote:
As Perrin said, it sounds like it might be a scoping issue with some variables
and how they are (not?) passed into subs. What could really help us spot it
are your subs and calls to them. In fact if you can reduce it to a very simple
test case that has the same experience, it would be easier to spot.

Michael Peters
Venzia

> OK, here's some code:
> 
> # systems
>      my @statuses;
>      my (@systems) = Lib::Systems->search( cid => $cid );
>      unless (@systems) { $self->model->log('debug', "systems for '$cid' not
found"); $self->context->throw( 'systems.not_found', 'Systems not found' ); };

> 
> Thanks!
>  At 03:40 PM 5/1/2004, Perrin Harkins wrote:
>  Dave Boodman wrote:
>  I'm seeing an issue where I do an insert and upon subsequent requests,
certain children are not returning the newly-inserted data (row), while others
are. Restarting apache fixes this as does waiting for some length of time.
>  Sounds like you have a scoping problem.  You are probably accidentally
creating a closure somewhere that is holding onto old values.  If you can
reduce your code down to an example small enough to post here, we can try to
spot it for you.
> 
> - Perrin
>    -- Report problems: http://perl.apache.org/bugs/ Mail list info:
http://perl.apache.org/maillist/modperl.html List etiquette:
http://perl.apache.org/maillist/email-etiquette.html
------- End of Original Message -------


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Mime
View raw message