I was shocked to discover that my co-author had plagiarized from the 
(online, copyrighted) MySQL Manual, High Performance MySQL 2nd Edition
(copyrighted by O'Reilly), Wikipedia (allowed to be cited without permission, but was not cited) and several websites.  Especially since I was the
first to discover this plagiarism, and we were in the "final editing" stage.
If I hadn't fixed that and gone on to check every single chapter using an
account I paid for at http://writecheck.turnitin.com, it is very possible
that my reputation would have been sacrificed by Keith's plagiarism.
<BR><BR>
I cannot be sure of that, of course.  What I am sure of is that Keith's plagiarism was not a mistake; he has plagiarized work in the past.
<BR><BR>The other thing I am sure of is that there is no plagiarism in the book at all; I bought a few "Thesis" level packages from <A HREF="http://writecheck.turnitin.com">http://writecheck.turnitin.com</a> and found many more instances of plagiarism, not just what the technical editor found from High Performance MySQL, 2nd Edition and not just what I discovered blatantly copied from the manual.
<BR><BR>
I spent a lot of time in January fixing the plagiarism I found -- even after Keith went back and supposedly fixed everything.  I took 6 days off work in January to be able to finish fixing the chapters.
<BR><BR>Currently I see that Keith is offering MySQL training through <A HREF="http://paragon-cs.com/training">http://paragon-cs.com/training</A> and the "Curriculum" section looks a lot like our Table of Contents.  We have both signed "exclusive and full rights" to the book's content over to the publisher, so Keith cannot legally use any book material without permission of the publisher.  Given how similar the table of contents is, I believe he intends to use book material without permission.  I doubt very much that he could prepare a course in 6 weeks when he could not properly (without plagiarism) prepare his half of the book in 6 months.
<BR><BR>
I had to spend an unexpectedly long amount of time fixing plagiarism, and I believe he is turning around and uses that effort for his own professional and financial gain.  Morally, I object to Keith using material from the book -- even if the publisher does grant him permission, and thus he can legally use material.
<BR><BR>
A colleague mentioned Keith had plagiarized his slides -- slides that had a Creative Commons license.  That means that all Keith had to do was take the slides and attribute them to the author -- there was no need to request permission, just attribute the author.  Perhaps that was seen as a "whoops" by the original author, but certainly I cannot stand by when I came so close to being a co-author on a book that included a lot of plagiarized work.
<BR><BR>So let this serve as a warning -- do not plagiarize.  It will come out, even if it does not become public the first time you do it.  
<UL>
<LI><A HREF="ch02TE.doc">ch02TE.doc</A> is the Word-format document after 
coming back from the Technical Editor.  This is what I received; and the
first time I read the chapter.  You can compare the document to the MySQL
Manual.
<LI><A HREF="writecheck.html">writecheck.html</A> is the report from http://writecheck.turnitin.com of "uncited sources".  It does not show what other site(s) this came from, so after seeing this I had to Google search for where exactly this content was.  (There are false positives with regards to MySQL error messages, or when a SHOW CREATE TABLE output from the sakila sample database is shown.  However, this particular chapter had a lot of plagiarism in it, which you can compare to the manual yourself.</a>  
<BR><BR>
The WriteCheck report has yellow boxes around sections that seem to be uncited sources, and the bold/brown text denotes the exact matches.  For example, #1 is probably a false positive, but box #9 is a direct plagiarism from <A HREF="http://dev.mysql.com/doc/mysql-linuxunix-excerpt/5.1/en/linux-rpm.html">http://dev.mysql.com/doc/mysql-linuxunix-excerpt/5.1/en/linux-rpm.html</a>.
<BR><BR>
There are some sentences stolen from the manual, but starting at change #19 you can see that whole sections were copied and pasted directly -- though he remembered to change "we" to "Sun", he did not change section references, for example:

<BR><BR>#71 - <I>See Section 2.3.7, "Creating an Option File".</I>
<BR>#116 - <I>Otherwise, use the passwordassignment procedure given in Section 2.10.3, "Securing the Initial MySQL Accounts.".</I>
<BR>#160 - <I>If you are using the MySQL Installation Wizard, start the wizard as described in Section 2.3.3, "Using the MySQL Installation Wizard"</I>
<BR><BR>
</LI><LI><A HREF="firstKeith.html">firstKeith.html</A> is the first e-mail conversation I had with Keith.

</LI><LI><A HREF="firstPublisher.html">firstPublisher.html</A> is the first e-mail conversation I had with the publisher, including a few examples of plagiarized sections.

</LI><LI><A HREF="PublisherKeith.html">PublisherKeith.html</A> is the conversation the publisher had with Keith.

</LI><LI><A HREF="ToC.html">The table of contents,</A> from our introduction, as it stands on Feb. 13th, 2009.  Since then we've changed it to 4 parts, but I don't have the document for that as it hasn't been sent back to me as of this point in time.  This is provided for comparison with the "Curriculum" of the course Keith is offering.

</LI><LI><A HREF="training.html">The training page copied from <A HREF="http://paragon-cs.com/training">http://paragon-cs.com</A> -- some of the images are missing, and styles, but the curriculum section is clearly extremely close to the table of contents of the book, as shown in the previous item, which makes me worry that Keith is using the content without permission.  And even if he is using the content with permission, I have a moral objection to it.

</LI></UL>