RE: [PEAR] Problem using PEAR::DB

> > Did I miss understand the problem? No, you're right. > Well being able to send multiple queries is one thing, but > being able to > read the results of the query are another. However I think it > makes few > sense to be able to send queries for which you never get a > result back. Yes, good point. It's truly inalienable getting back information about the result of statements I sent in a batch query, because otherwise inconsistency might be fostered or script routines abort/zero-reply by chance. > Well I am pondering the suggestion a bit. Maybe with a separate method > like batchQuery() it could be feasible. Would be best, while this way you are able to rely on the existing features instead of changing the code which -at least for me- works fine. Thus you get a clean distinction between batch and single statement query. I'm at the moment forced implementing an extension and am doing quite similar to your idea. <snip/> > I looked at the phpmyadmin code and found the relevant section, but > phpmyadmin code is god aweful ugly. The code brought me sleepless nights, too. It's really a mess. Though working -somehow. Best Regards Dennis