Re: MS Access 'equiv' for Linux?

From: Christopher Browne (cbbrowne_at_acm.org)
Date: 04/07/05


Date: Thu, 07 Apr 2005 11:31:29 GMT

After a long battle with technology, "prg" <rdgentry1@cablelynx.com>, an earthling, wrote:
> Christopher Browne wrote:
>> >> 8) StarOffice Adabase.
>> >
>> > I think this is pretty much dead/legacy at this point. Adabase and
>> > SAP (now offered by MySQL) have suffered from lack of adequate
>> > (especially English) documentation. Feature set is pretty
>> > impressive, but like all dbs, they have their peculiarities which
>> > _must_ be documented to make full use:(
>> >
>> > SAP may finally provide the MySQL guys with "real" relational db
>> > capabilities.
>>
>> Any integration with StarOffice would be about equivalent to what
>> you'd get with PostgeSQL+OpenOffice.org
>>
>> And I don't see the move of Adabas-D (which was only one of
>> Software AG's products; they still sell Adabas!), renamed to
>> SAP-DB, now sold by MySQL AB as MaxDB(tm) to be an indication of
>> continuing or forthcoming success for it. The codebase for SAP-DB
>> was really quite painful to look at let alone work with. I cannot
>> imagine that MySQL AB will be able to get anything meaningful out
>> of it to integrate with their products. All I can see happening in
>> the short term is for there to be enough cash flow from supporting
>> SAP-DB and MaxDB(tm) licenses for them to keep enough developers on
>> staff to keep it from going totally moribund.
>>
>> And the only value I can see to the MySQL/SAP-DB deal is if the
>> support involvement gives MySQL AB a vehicle to figure out what are
>> the minimal capabilities that they can add to MySQL(tm) in order to
>> make it into a reasonable host for some Adabas-D/SAP-DB
>> applications, probably most notably SAP R/3. In the case of R/3,
>> there _isn't_ that much that would need to be added, as it
>> traditionally makes minimal use of anything more than the most
>> primitive of "relational" database features...
>>
>> "Success" would be defined as making MySQL(tm) sufficiently
>> functional that they could get SAP AG to use them as a bludgeon in
>> the next round of gory negotiations between SAP AG and Oracle
>> Corporation.
>>
>> (FYI: The above is the only reasonable scenario that has fallen out
>> of considerable puzzling over the way MaxDB(tm) has fallen to
>> MySQL.)
>>
>> Aside from that possibility (which would be exceedingly messy, and
>> would point to the free software community being a mere stepping
>> stone for all parties involved), I just can't see the use for the
>> Adabas-D code at MySQL AB... --
>
> Agree completely. Better summary/details than I could come up with
> in such a succinct package. Can I quote you?

Yes, more-or-less that summary has been outlined a couple of times on
one or another of the PostgeSQL mailing lists. Quite a bit of
curiosity was elicited when MySQL AB received about $20M of venture
capital at around the same time they started the MaxDB(tm) effort.
People got the impression that this was about SAP investing $20M in
MySQL AB, though that's not the case.

It's not possible to be certain that what is outlined is the exact
reality of things, but nothing else has made as much sense.

> I have the same questions re: MaxDB and the folks at MySQL as well
> as the further development of SAPdb by SAP for their ERP/CRM
> solutions. Why take yourself off the $10,000,000 table for the
> Fortune 500 because they aren't that interested in
> yet-another-db-backend?

> It _will_ be interesting to see just what comes of the many recent
> db "donations" to GPL. Still, it's an _awfull_ lot of work just
> getting familiar with the code. And cross-breeding ???

The problem is that a lot of the stuff falling out of companies doing
"GPL releases" is that the results still remain strictly proprietary
to the companies that own them. I can't take MySQL(tm) and "do my
thing" with it; that would get me sued by the owners.

Pointedly, you can't get the "free software" effect of taking bits of
one and combining it with bits of the other. Cross-breeding? Uh, uh,
not gonna happen. Combining bits of MySQL(tm) with FireBird and with
Zope would require that all involved give up proprietary rights.

-- 
(reverse (concatenate 'string "moc.liamg" "@" "enworbbc"))
http://linuxdatabases.info/info/lsf.html
Rules  of  the  Evil  Overlord  #231.   "Mythical  guardians  will  be
instructed to  ask visitors name,  purpose of visit, and  whether they
have an appointment instead of ancient riddles.
<http://www.eviloverlord.com/>


Relevant Pages

  • Re: Datenbank SQL-Server vs. MySQL
    ... > OK to argue against mySQL is easy, you always can argue of missing ... SAP DB is ADABAS D. Software AG was failing and decided to exit the ... in the database business and started to look for ways to keep SAP DB going ... industrial strength you have to use the InnoDB storage engine. ...
    (microsoft.public.de.german.entwickler.dotnet.datenbank)
  • Re: MS Access equiv for Linux?
    ... I'm not a MySQL fan ... And I don't see the move of Adabas-D (which was only one of Software ... they still sell Adabas!), renamed to SAP-DB, now sold ... probably most notably SAP R/3. ...
    (comp.os.linux.misc)
  • Re: MS Access equiv for Linux?
    ... I'm not a MySQL ... > licenses for them to keep enough developers on staff to keep it from ... > the minimal capabilities that they can add to MySQLin order to ... > of gory negotiations between SAP AG and Oracle Corporation. ...
    (comp.os.linux.misc)
  • Re: Non GPL Python MySQL Client Library.
    ... > worlds 3rd largest Software Company SAP. ... that MySQL AB essentially took over development of SAP DB (MaxDB by ... preferring to stick to a core business of supporting ...
    (comp.lang.python)