Re: adding bug info infront of sql query

Jon Parise wrote:

If someone wants to put such stuff in their own queries, that's up to them. I'd rather not have to deal with that on the package end of things.

Agreed, although I do think it would make an interesting option that the end user could toggle at the package level without modifying all of their queries at the package's entry points. Heh :) Clearly, I thought the interesting part of it was the actual bug. I don't think the file/line stuff is that interesting in the query, especially if it's being added by PEAR DB/MDB. (How could that info be added to reflect the context in the calling code w/o using something like debug_backtrace()?) I'd also be curious to know at what level MySQL query caching operates -- i.e. one would hope that comments would be stripped before checking to see whether query has already been compiled, but for other caching layers there's potential for these comments to make the same queries look different.

For my own part, I'm always nervous about adding too much information about my source files (filestructure, etc) in anything being sent over the network. Hans