"Alaric B. Snell" <abs@frontwire.com> writes:
> Either way, can it do any *harm*? :-)
Certainly. For example, suppose some app is using a setLong parameter to
output a constant that's actually being compared to an integer column.
Right now, this works (for "work" = "can be indexed"). With your
proposed hack, it wouldn't.
I realize it's pretty annoying to have to work around this at the
application level. However, the app at least knows what it's doing,
ie, what data it's got and what the database column it's interested in
is. Eventually, the backend will solve the problem correctly --- it
also has all the relevant information. JDBC is the one place in the
chain that *cannot* solve the problem because it doesn't know enough.
Thus, a solution in JDBC cannot be a real solution, only a
broken-by-design kluge.
regards, tom lane
