|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Why MySQL is used instead of MaxDB?
From: David Brady (maxdb
ferriel.com)
Date: Mon Apr 05 2004 - 13:07:35 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]