Database query caching not working

[eluser]TheFuzzy0ne[/eluser]
[quote author="fchristant" date="1242945044"]- The bug I reported above. when using the db class as designed (using parameter replacement, a standard practice) and enabling caching, it does not work. I cannot believe this is not tested or found by someone else. Is everybody hardcoding SQL?[/quote]

As far as I know, Active Record is very popular, but there are some hardcore minimalists who prefer to use straight SQL. I'm willing to bet that there are even fewer people who use query bindings (perhaps this would be an interesting poll?).

[quote author="fchristant" date="1242945044"]- Transactions. A previous disappointment I had was with transactions. Cache seems to influence it and nested transactions don't work, which is a showstopper if you need transactions, you want those for reliability. I had to go in and patch the core to make that work.[/quote]

I'm a bit confused by that. Nested transactions shouldn't be a problem, so long as you're database storage engine supports transactions. If you're using transactions, you're making write-type database queries. Cache on the other hand relates to read-type queries. I fail to see the correlation between transactions and cache. Am I missing something?