> | Is the first result set getting crapped on? Any alternative > | approaches? > > I've had this problem too. I 'fixed' it by using two DBI handles which > works but isn't ideal if you have Apache::DBI running because you end up > with twice as many persistent connections kept open. :-(
There is a simple solution: stop using the DBI plugin! Write a little bit of perl code that does the DBI stuff and passes the results to your template. Cleaner, faster, and no weirdness. SQL embedded in HTML... *shiver* It reminds of the horrible Illustra Web Datablade product that I used to have to use. - Perrin
