[sclug] URL encoding/decoding question

[Pieter Claassen]

> all. This being the case, switch to BLOB or equivalent and let Java take
> care of the conversion. Once you remove one entire layer of character
> interpretation, your problem will either vanish, or become a while lot
> simpler to solve.
>
> - Raz

To tell you the truth, I have long ago switched to a BLOB with MySQL 4.0
to get rid of the utf8 issues but didn't have any luck with that (i.e.
still had the character mangling on the browser->db->browser round trip).

The current situation with MySQL seems to be that it doesn't support
preparedstatement with query caching so even though you can switch query
caching off in 4.1, it is difficult to confirm that it is actually being
disabled.

The issues seems to be that (quoted from MySQL site
http://dev.mysql.com/doc/refman/4.1/en/query-cache.html)

Note: The query cache is not used for server-side prepared statements. If
you are using server-side prepared statements consider that these
statements will not be satisfied by the query cache. See Section 17.2.4,
?C API Prepared Statements?

-Shock, horror!!!!!!

As far as I am concerned, this breakes Tomcat authentication completely.

Any workaround suggested? Well, other then move db's? postgress is
starting to look REALLY attractive!

Cheers,
P