Re: mdat + udat = hang
At Wed, 22 Jan 2003 10:57:40 -0500 (EST), Joshua Spoerri wrote: > Are there any issues with using mdat and udat in the same page? > I've been using udat for a while with no problems, and mdat also seems to > work fine on its own, but mdat and udat in a single page cause the server > to lockup. > > I'm using Embperl 1.3.4, Session 1.54, SessionX 2.00b3. I'm using mysql > for session storage. try using something other than sysv semaphore locking (eg filelocking). its possible to get hash collisions with the Apache::Session sysv semaphore locking code, which means both %udat and %mdat try and grab the same lock. (afaik this hasn't been fixed or worked around in Apache::SessionX yet) -- - Gus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: importing subroutines with Execute()
At Thu, 23 Jan 2003 20:33:57 -0500, Kee Hinckley wrote: > I wish more of that were transparent. Haven't looked to see what's > happening in Embperl 2 mod_perl 2 allows you to have a separate perl interpreter for each virtual host, so you can't step on each other toes even if you want to. (according to the docs at least, i haven't actually played with mod_perl2 yet) -- - Gus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Installation problem
At Wed, 22 Jan 2003 18:46:44 -0500, winfield henry wrote: > Below is the output from a attempt to install Embperl 1.3.4 on a system with > the following > Redhat 8.0 (psyche) > httpd-2.0.40-11 > httpd-devel-2.0.40-11 > mod_perl-1.99_05-3 > > Seems to be looking for the Apache/src.pm file but can't find it. It is not > on the system anywhere. A similar error with previous versions of apache was > solved by installing apache-devel, but the devel package is installed here > and there is no such file. Any suggestions appreciated. Apache::src is from mod_perl 1 (mod_perl 1.99 is a prerelease of mod_perl2). embperl 1.3 doesn't know about apache2/mod_perl2 -- - Gus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Display using array ref of NULLs in dynamic table
At Fri, 24 Jan 2003 16:54:24 +1100, Jim Hall wrote: > After selecting a set of data using the following: > >... >$dat = $sth_rte_sel -> fetchall_arrayref; >... > > and then attempting to display in a table: > > > [+ $dat->[$row][1] +] > [+ $dat->[$row][3] +] > [+ $dat->[$row][4] +] > [+ $dat->[$row][5] +] > [+ $dat->[$row][6] +] > Value=Ed > it> > > > I'm finding that if a record contains a field with a NULL value then > the whole record is not displayed. > Is there a way of turning off this behaviour? you could turn it off by setting $tabmode = 20 and then $maxrow = @$dat, but thats too hard (and likely to upset other Embperl pages). typically you work around it by doing [+ $dat->[$row][1] || '' +] in places you expect to find a NULL. obviously you can't do this for every column or the row loop will never exit. if you may have NULL's on any cell (or don't know what to expect) then you have to do each row separately like so: [- $r = $dat->[$row] -] [+ $r->[1] +] [+ $r->[3] +] and if you're going to do each row separately, then you may as well not keep all the rows in memory (unless you need to use the results somewhere else): [- $r = $sth_rte_sel->fetch -] [+ $r->[1] +] [+ $r->[3] +] -- - Gus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
