On Tue, 16 Jun 2009, MK wrote: > If I can't find a better solution, I will just have to work around this > by breaking the page into seperate components -- since all my other db > insert calls work, the only thing I see different in this page is the > length and number of (potential) db operations, etc. Since only one of > the potential operations will take place, I can't really blame DBI and > believe the page is just "too much" for mason to correctly parse*. > That is not a very satisfying solution!
Just ot be clear, Mason does not parse the Perl portions of a Mason component, other than to find where said portion ends. What Mason does internally is turn a component into a bunch of Perl code which gets eval'd. The Perl portions of the component are effectively inlined with the generated code. So if you have a problem with the Perl portion, chances are that 99.9999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999% of the time it's your code, not Mason. Of course, the _context_ in which your code gets executed can sometimes be an issue, if you have expectations about the environment that are not correct. -dave /*============================================================ http://VegGuide.org http://blog.urth.org Your guide to all that's veg House Absolute(ly Pointless) ============================================================*/ ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
