> > Yes, SQL sucks awfully bad. However it doesn't have to be typed, which does > make things a lot less silly. See http://www.sqlite.org/datatypes.html for > info on how SQLite isn't typed. I'm not completely up to speed on the > relational model, but I see no reason that it would need typing. It sounds > like it was invaded by the same people that are now trying so hard to > slaughter XML.
I think you guys have not dealt with large data processing systems which have enterprise-wide or larger scope, lifespans of decades, and often involve 1000's of developers at various points. Even in smaller-scale systems data typing is a very useful and often necessary thing. I mean just as an example, how could you reliably SUM() columns in a relational database if the integer type was not enforced? Data could be who knows what! Now you are going to foist off the job of making sure only integers go into that column on the application developers or the users? Good Luck! Databases got strong typing, integrity constraints, etc. because when you build these big databases with data flowing into them from all over the place you NEED to be able to have that database insure its own integrity, trust me! Then there are the issues of moving data around between databases and between vendors, etc. Anyone that builds real serious IT solutions and doesn't believe in data typing is bound to end up in a nightmare eventually. More likely nobody in the business world will be foolish enough to deal with you... -- Tod Harter Giant Electronic Brain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
