It is defenitely the only way to protect people who are using SAP/DB in production. Count me in, I would like to help this project.
Cool.
The question that arises is will SAP AG allow us to use SAP/DB name? The likely answer is no. So we will have to come up with a meaningless name, the way Firebird people did. And even with SAP's name on it this database was underrated for its merits.
How about XAB DB? However, let's hope we can avoid forking the kernel and only maintain an LGPL'ed client lib.
I am willing to help but I've looked at source code. I don't think we will be able to find enough people to work on it.
Well the thing to remember that the only thing we would have to fork is the client and as the mysql/sapdb sources are GPL'ed it's relatively easy to figure out what changed and reimplement that in the client lib.
(not-my)SQL AB starts to change the kernel side of things so it doesn't work with the normal client lib then it's possible to revert those changes and re-compile the kernel thus allowing all old sapdb clients to keep working with the newer mysql infected kernels.
-- Regards Flemming Frandsen - http://dion.swamp.dk PartyTicket.Net co founder & Yet Another Perl Hacker
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
