SQL for Web Nerds
philip.greenspun.com
philip.greenspun.com
Lo and behold, the modern era of youtube and google video has seen the resurrection of these videos. Someone named "Chao Xu" has uploaded (nearly) all of the videos to google. see http://mgccl.com/2008/04/06/aduni-videos-now-on-google-video
(in fact, there's even a course on databases)
http://www.archive.org/details/arsdigita
EDIT: actually its only the first 8 courses (there are 12 total).
EDIT: wrong again; they have all 12 courses, but only list the first 8 on the landing page.
If this is not a relational database this is still true. Correct? For instance, Google App Engine, pretends to be not a a table http://stackoverflow.com/questions/4731657/google-app-engine... but it is still a table with columns and rows.
For instance with Google App Engine there is no way to say, My columns are foo and bar then have it tell you that you've done something wrong when you try to insert something into column baz.
Unlike traditional relational databases, the App Engine datastore doesn't require data kinds to have a consistent property set (although you can choose to enforce this requirement in your application's code).
Here is what they mean by that. In a traditional relational database every table must have a table definition that specifies all of the columns and column types. In the App Engine it is up to the application to supply an implicit table definition. And there is no enforced consistency. If two applications access the same table, they can put entirely unrelated kinds of objects there. (Or, worse yet, put related objects that are just slightly different. Just to confuse you.)
In practice it isn't perfect. There are times that the database does things wrong, and it is useful to have a bag of tricks for figuring out when it is going wrong and forcing it to do the right thing. But on average it does much, much better than most developers could, and does it with a lot less work.