Beginning HTML with CSS and XHTML incorporates practical examples that will show you how to structure your data correctly using (X)HTML, together with styling and layout basics using CSS. It also shows how to add dynamic behavior to your data using the JavaScript. language. All of the featured code and techniques are standards compliant and demonstrate best practices.so you will not waste time on any outdated techniques.

Errata Submission

If you think that you've found an error in Beginning SQL Queries: From Novice to Professional, please let us know about it. You will find any confirmed erratum below, so you can check if your concern has already been addressed.

Errata

Issue	Author's Response
For Chapter 4, p. 64, listing 4-7 and listing 4-8, I tested it on MSAccess 2003, both give the same answer (i.e. 228, appear twice, 286 appear 3 times in the result). Am I getting anything wrong? Regarding you books, honestly speaking, you save my life, both of them give me a very good introduction and intermediate level of detail why the RDB "need" to develop in the current way. A very detail, step-by-step explaination. Without them, I can't understand what my DB lecturer is talking about. Thanks After these two book, I'm hoping you can write an real advanced level db or SQL, especially on relational algebra, so that people like me can understand those abstract concept.	NO you are not doing anything wrong. If you look at the example output on page 65 I get the same results. I have just ordered the rows by tournament type so we can compare the different types of tournament retireved. Thanks for the encouragement and good luck with your studies. Clare
Chapter 2, p. 36, Listing 2-27. SELECT COUNT(DISTINCT Handicap) FROM Member This query works properly with Oracle, but doesn't work with Access. How should I modify it for Access?	See page 136.
This is about chapter number 3. The definition for outer join is incorrect ..it should say that include tuples that either does not have matching rows in other tables or have null in join attribute. Otherwise say if the Type table has another row for Associate with fee 50 and there is no matching row in Member table and treat the Typpe table as right table and apply right outer join .. then in cross join there be no row where join attribute is null but certainly associate does not match with any row from member table.	Thanks. I could have been clearer :-)
Chapter 4, p. 64, listing 4-7. I believe that this 'NOT IN' sub-query is conceptually sound, that it correctly finds records in the Entry table that are not associated with ANY 'open' tournament. It is not equivalent to the erroneous query in Listing 4-8, p.65. Yet the discussion on pages 65 and 66 seem to indicate that it is wrong. I refer specifically to the sentence, "The same members will be retrieved by the query in Listing 4-7, which uses NOT IN". This is not correct. Now, NOT IN with NULL data is dangerous, but NULL or missing information is not specified as existing in the data and being a source of potential problems. It isn't part of the discussion on these pages. In short, I think that the discussion around Listing 4-7 needs a little clarification, as it is not contain an error in logic as that Listing 4-8 does. On the whole, the book is very fine. I like especially the way SQL is related to relational calculus and relational algebra.	Thank you very much. You are quite right. Can't think how that sentence got past so many proof readings. Listing 4-7 returns the set in Figure 4.3a and listing 4.8 those in 4.3b. Have i got that right now??? How embarrasing. Glad you like the calculus and algebra approach. HAve been getting a bit depressed by very negative reviews on that apporach on Amazon. Oh well. Cheers Clare