On Mon, 16 Jun 2003, Edgar Castanedo wrote: >I have been playing with both Oracle and SAPDB lately. I am trying to figure out >which one I want to invest my time and energy in. The problem is, I am torn between >the two right now. > >I know that Oracle is huge and is not going anywhere. I know that SAPDB is rich in >it's feature set, but can the same be said about it's lifespan? > >The reason I am giving SAPDB a chance is because I like what I see so far, plus the >fact that it is open source kind of sold me. I am a big open source fan. If SAPDB was >not open source, I would have just ended-up using Oracle and sticking to it. > >With that out of the way, I hope to hear some insight into what everyone thinks on >how Oracle and SAPDB compare. I want to make SAPDB my primary database, but I feel >like I need some sales points. > >Can someone tell me how Oracle and SAPDB compare and what would make me want to >choose SAPDB over Oracle. (Even if it is just a reference to a web page). > >Thanks In Advance...
Maybe (maybe... not sure) oracle is less buggy. We develop under postgresql here, beacuse it's quite user-friendly, but are seeking for a good DBMS. Haven't found any so far... Right now there is a bug in sapdb which stops me from using it: left join does not work properly. And that's just the beginning; there may be other bugs, which I couldn't found beacuse of this one. I'm testing mysql now, it has an extension (or whatever) called innodb (see www.innodb.org), which supports row-level locks, transactions, foreign keys, etc, apparently everything we'd need. In worst case, we may still stick to postgresql, if innodb fails, too. These are my experiences. To answer your question, if you have to make the decision now, you'd better stay with oracle. Agoston Horvath _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
