I went through most of the docs, but found them sparse and scattered. They
desperately need a rewrite.
I also found mention that SAPDB does not support versioning, which means you
can get inconsistent reads (not ACID). It also does not have text-searching,
as PosgresQL and MySQL (but not InnoDB) do.
SAP is pouring money into it, however, and has alot of developers. They need
to get some key features in place, however. First, some sort of
high-availability (PostgresQL needs something more solid as well; Oracle
definately leads here). Second, good docs. Third, ACID. Fourth, a decent
build process (get this - it's written at least partially in Pascal, and
they have a pre-processor that turns it into C, which is then compiled;
apparently the build process is unusably cryptic and thus not very
accessible to anyone outside SAP).
David
----- Original Message -----
From: "Alvaro Herrera" <alvherre@dcc.uchile.cl>
To: "David Griffiths" <dgriffiths@boats.com>
Cc: <pgsql-general@postgresql.org>
Sent: Thursday, April 03, 2003 4:45 PM
Subject: Re: [GENERAL] SAPdb vs. Postgresql
> On Thu, Apr 03, 2003 at 11:58:57AM -0800, David Griffiths wrote:
>
> > SAP is strange. The setup it unusual, and poorly documented. The usage
is
> > poorly documented. Finally, when we went to use SAP, it worked for a
while,
> > then the database seemed to get corrupted.
>
> I've heard about that. A gratis accounting application very promoted
> here in Chile uses SAPdb as it's backend, and apparently the driver
> manages to corrupt the data somehow. It's usable now, and becomes
> unusable tomorrow. I wouldn't trust such a RDBMS, no matter how much
> features has it got.
>
> I also tried to compare it to Postgres, but the lack of documentation
> didn't precisely help me get started, and it was only a hobby so I never
> came to it.
>
> --
> Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
> "Estoy de acuerdo contigo en que la verdad absoluta no existe...
> El problema es que la mentira sí existe y tu estás mintiendo" (G. Lama)
>
