I already thought about warning the user if he is comparing strings with integers or vice versa.

But as I said I want to play safe not to loose any information in the process.

SQL is far too diverse to rely on assumptions, from what I know is DBI highly depended on the quality of the underlying DBDs, like emulating placeholders where not available.