Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
SQL is unfortunately tied fairly tightly to an RDBMS implementation. All those "join" statements, various ways of expressing "constraints" such as "foreign keys" - all are considered "integral" parts of SQL.
No, you don't have to provide them. A Post-Relational like Amazon SimpleDB could, theoretically, use SQL for querying and just trim back the feature-set.
But perhaps it'd be wiser to look at a query language more specific to the Post-Relational model?
Perhaps SQL stopped being "SQL" and started being "Structured Relational Query Language". *shrugs*
Is it spending 3 weeks drawing diagrams that, in 3 more weeks, won't represent the true state of the system at all?
You draw your diagram. I'll spend 1 night doing a rough-shot prototype. I'll "hack" it.
Then I'll use that prototype when I create a well-architected system. Then, since I share my stuff lots, other "hackers" will help improve that design.
Be careful when you discard one set of "propaganda", and listen blindly to another. Maybe "hackers" aren't so "evil" after all. After all, I don't remember signing up for any cult.