Am I alone in thinking that a division operator that does
different things depending on the declared datatype of a
column is an abomination?
Absolutely not.
Of course he won't be alone, doesn't make him ( or you ) correct or in fact
incorrect.
I think allowing mathematical operators built into databases in the first
place is an absurdity, but many will disagree with me ... and agree with me.
So what?
I'd much rather used a stored procedure for implementing my own tightly
coupled operations that rely on database providers to continue to expand
their products into a realm where subjectivity plays such a big part.
However, the mere thought that someone would use an operation where two
declared Integer values used in that operation could create a Real value
without explicity declaring that you are using Real operators to do it makes
me shudder. Operators are always, without fail, contextual, when they exist
for multiple types. Whether you keep the same name or not for the operator
is an issue that is best addressed by a standards body, IMHO.
Use a hammer for hammering, and a screwdriver for screwing ( screws ).
Dave.
