In the last exciting episode, "Sean Mollet" <[EMAIL PROTECTED]> wrote:
> Richard:
> You shouldn't have to change any of your sql's unless you want to. MySQL
> supports such a limited subset of the true sql standard (sapdb supports a
> much larger one) that none of the queries you run against it should have any
> trouble running on sapdb. Additionally, if you have your indexes set up
> well, sapdb should be noticeably faster.
That's not /quite/ accurate...
What happens, in practice, is that "entry level SQL" is so primitive,
/everyone/ winds up implementing extensions on top of that, even
including MySQL.
Handling of sequences/autoincrementing-things is a good example of
this.
The result is that you are almost guaranteed to get tempted to use
some features that are specific to whatever DBMS you picked first, and
so will have some porting effort in moving to another DBMS.
--
output = reverse("moc.enworbbc@" "enworbbc")
http://www.ntlug.org/~cbbrowne/multiplexor.html
"... and the REALLY GOOD THING, is that after you have gone to the
trouble of compiling that once, you can run it MANY MANY times!!!"
-- Arthur Norman
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
