Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Journal of jjore (6662)

Tuesday October 03, 2006
04:21 PM

Argh! PMT_ID != PMTDBT_ID!!

[ #31209 ]

This is the second time this week that I've used a SQL join like

PMT.PMT_ID = PMTDBT.PMTDBT_ID

but meant to say

PMT.PMT_ID = PMTDBT.PMT_ID

. Both values are of type NUMERIC but I wish Sybase knew that their domains are unrelated and that each were of a distinct type PMT_ID and PMTDBT_ID or similar.

That way it'd just be invalid to compare the two unless I somehow defined a way to convert from one of those types to the other.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • As I understand it from C.J. Date's description of the relational model, each column must have a name and a type. Operators must be defined for each type and if types don't have an operator defined which allows them to be compared, the SQL doesn't even compile. If that were true, the following mistake would never happen without an explicit typecast:

    SELECT name FROM customer WHERE age > id

    Admittedly that's a trivial (one might say ridiculous) example, but it illustrates the ridiculousness of the und

    • Exactly. I thought briefly about linking to something you'd written before about this but mostly I wanted to complain that I'd been bitten by this typo twice within a week.

      It sucks.