- maintain GPL+LGPL licenses as is (GPL for kernel and so on, LGPL for interfaces - JDBC, ODBC, Perl, Python and so on);
I am working on a compromise for this now. I am fairly sure that it will not make everyone happy, but it should address some of the concerns that we have.
I will await the result of your work.
As far as i know, all that we worry about, is that we want to use/redistribute the client-libs without paying for them.
- second, don't change any existing code related to SQL syntax (excetp additions: they will be welcome);
Ok. Their may be changes - however, we also want to keep things as unchanged as possible for the short term integration.
There is ANSI-SQL, and that should be _the_ standard for both: SAPDB and MySQL.
If there are special features which sytax differ between MySQL and SAPDB, than a decision has to be made.
- don't touch transactional processing. We loved sapdb way to do the work with transactions. I've servers running 24x7 and even in completely failure, I never lost no one field data...
As far as i know, SAPDB just respects the ACID-rules.
I will prepare a document that talks about the advantages and disadvantagesI'm not starting a fight against MySQL, is just a fact the several of us has take months to explain way SapDB should be used over other databases, like MS SQL, Oracle, DB2, PostgreSQL, and even MySQL. The first of tree are obvious: they are paid (too much paid). The other two aren't to obvious, and we had more trouble here identifying theirs "why or why not" tecnically.
of the partnership that can be used to help advocate the adoption or
continued use of the MySQL/SAP DB technology in a corporate setting.
Hopefully this will help ensure that you have less trouble using the product in your work setting.
This is a problem that i certainly have too.
Every other company i know uses MySQL, and they all ask "why SAPDB". My answer is short: "it offers referential integrity and transaction". Often i hear answers like "what's that for". Many people don't care about DB design - that's why MySQL version<3.x isn't that unpopular yet.
Also, it is rather nice to be working with the SAP DB community. As a group, you seem to be committed to the database and are willing and able to express
your wants and concerns. This makes it much easier for everyone who is
involved to try and solve problems.
I hope i'm not to rough sometimes, but don't take it personally - we just want to be the new MySQL to be as good as SAPDB.
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
