I concur with all comments made about the Documentation, however, I would like to write on a positive note here. I'd simply like to say that, where so many companies are afraid to admit product faults, and give little advice to their users, the people behind this mailing list go out of their way to find answers to all your questions, and do admit shortfalls when they occur.
Well done Daniel and team. -----Original Message----- From: David Brady [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:08 AM To: [EMAIL PROTECTED] Subject: Re: Why MySQL is used instead of MaxDB? John L. Singleton wrote: > > Assuming all things equal, the real breaking point is in the > *documentation*. It needs to be easy to use, easy to understand, and > informative. The problem is, IMHO, that people new to MaxDB find the > documentation system very very difficult. Not just to use, but to > understand as well. Amen to this. I've just starting testing MaxDB for some internal reporting tools. (And had tried about a year ago with SapDB but gave up.) Though the documentation is complete and accurate, it is almost impossible to use. Biggest problem is that almost all of the information is supplied as tiny little syntactically correct blurbs - i.e. an extreme version of a reference manual. This sort of presentation is nice once you know the product, but, at first, it is like looking at vast landscape with 1 inch square blinders. You never get a feel for the big picture. -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
