When like is not what you like

I’ve been always using PreparedStatement in JDBC query operations for two main reasons:

• it manages for you all data translations between types
• it automatically calculates the best query path to recover your data

Unfortunately there’s a little canvas you should know about: we know, like is evil, but when you use like in a query using a PreparedStatement, data path is calculated before having information about what you would like, so resulting query is very unoptimized! In such cases you should proceed handling like parameters with string composition/substitution, before creating PreparedStatement object.

That’s not a JDBC or database fault, it’s just how things work. But you should be aware of it…

Speaking in Prague at CZJUG

On 23th I was speaker at CZJUG in Prague with Filippo, presenting the talk I’m gonna expose at JavaPolis in December

It was a great JUG meeting and also a nice test for myself I feared about my little knowing of english tongue, anyway all went on well and I’m satisfacted about my performance. Also Prague is such a beautiful city, and I enjoyed it very much: I discovered a charming beer, Kozel, a dark beer very tasty!

Thanks to Roman Strobl and CZJUG you may also take a look at the video of this speech here!