I'm not too sure how much use buying one of the standards would be, as meritoriuos they are. Virtually no server meets the (most recent) standards in their entireity, AND most servers have there own extensions and variations on the standard. So either, you use the reduced common set applicable to all db's, or get a specialist book on the db you are working with.
Personally I found the O'Reilly "SQL in a nutshell" a good basic reference But not a primer (it covers MySQL, Oracle, SQL Server (and one other I can't remember)). Its a bit sparse on examples (but that would be the same with a standards manual), but it provides sufficent pointers to jog the memory, or show the way forward. But there are others with masses of text, information and examples. The "in a nutshell" series are probably not the "best" for beginners, don't take offence I've made no assessment of your competance.
Last edited by healdem; 12-05-04 at 07:26.
Reason: aah shpelling mishtakes yet again
I'm certainly game with the idea of buying a book. As a general rule, they are significantly easier to read than the standards are!
Just as a note, the standards are what both the database engine writers and the book writers use for a reference. The standard is where they start. If you are looking for a clear, technically correct statement of what is required for a given level of SQL implementation, the standard document is where I would start.
The standard documents might not be suitable for everyone, but why start third-hand (with the interpretation provided by the book's writer)?
depends what cleverpig is trying to achieve. If CleverPig is going to write a SQL database then go to the standards to check what you are doing is correct, if CleverPig is writing some application software accessing a specific SQL engine then go buy a book relevent to that SQL implementation, or buy a book which identifies where varius flavours of SQL implementations vary from the standard and make sure Cleverpig writes code compliant to the lowest common denominator (if you wan ttomake your code protable).
The standard identifies what the server "should" do, but the servers often:- don't do it,
or dont do it the way the standard says they should,
or has implemented some other features not thought of at the time the standard was thrashed out, or has retained some features from previous versions which are not compatible with the current standard
even if they are compliant with most of the standard, they are still not standard compliant. On dodgy ground here but I'm not aware of any SQL implementation which is truly compliant to the satndards.
Thank for your replies..They are very good suggestion about how to get and learn sql standard..
I think the sql standard is a common role,but the some sql implement has his owner's role base on thie sql standard!..
So we can use it fixable just as you said..