Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Databases Programming Software

Daffodil DB / One$DB - How Do They Compare? 36

capt.mellow asks: "It's been mentioned that Daffodil Software has just released php extensions for their java-based commercial and open-source databases, Daffodil DB and One$DB respectively, enabling these databases as options for running web applications. Personally, I have never heard of these databases before. How do they compare to the likes of Oracle, SQL Server, MySQL, PostgreSQL, Firebird, SQLite, et. al.? Has anyone used them in web applications, and would they care to relate their experiences?"
This discussion has been archived. No new comments can be posted.

Daffodil DB / One$DB - How Do They Compare?

Comments Filter:
  • by FullMetalAlchemist ( 811118 ) on Thursday February 17, 2005 @06:54AM (#11697901)
    Sounds like good products.

    However, there already is SQLite and PostgreSQL that covers the entire spectrum; up untill Oracle is needed.
    As I unfortanly doubt that these databases compare to Oracle, so they are in essence racing with a dead horse; it really might be a beautiful dead horse, but it's still dead.

    I really like new things, but they are pushing their luck when introducing a database into an already overcrowded market.
  • by namekuseijin ( 604504 ) on Thursday February 17, 2005 @07:00AM (#11697909)

    But i personaly know PostgreSQL and MySQL, and would definetely go for the former.

    You won't be getting DBMSs so much better or more mature than PostgreSQL in the free software world. DBMSs of this quality don't simply spring into existence out of nowhere, hype notwithstanding.

  • its LGPL (Score:4, Informative)

    by johnjones ( 14274 ) on Thursday February 17, 2005 @07:04AM (#11697922) Homepage Journal
    some things to note

    you can try it out yourself....
    there is a comparision with derby
    http://www.daffodildb.com/onedollardb-derby .html

    everything depends on what you are using it for

    you dont say that in your posting

    if you did I might be able to compare and contrast

    regards

    John Jones
  • by ptaff ( 165113 ) on Thursday February 17, 2005 @07:58AM (#11698069) Homepage
    The product page boasts their RDBMS is written in pure Java.

    Databases engines must mainly do hardcore work on large sets of data (index, sort, merge, uniq, manipulate dates...); using Java for data crunching, is that really a neat idea?

    Aside from the needed feature set, speed is I think the most important factor when picking up a RDBMS. I guess this is one of the major reasons for the quick adoption of SQLite [sqlite.org] and the popularity of MySQL vs. PostgreSQL.

    Feel ready to own one or many Tux Stickers [ptaff.ca]?
    • Just some small questions about SQLite. I like the idea of it being really tiny and uses a single file as a database, makes is possible to ship a tiny DB with small applications.

      I am however doubtful of it's performance. It is clear from the performance measurements that SQLite is only faster than MySQL when it is running asynchronous or in transaction mode. AFAIK in both these modes, any problem in the SQL statement would invalidate the entire list of SQL statements. It seems than that in most practical s
      • No (Score:2, Interesting)

        by Pan T. Hose ( 707794 )

        In this light; is SQLLite really any faster than either MySQL or PostgreSQL in real-life, production situations?

        The short answer is: no. The long answer is: it depends on what you mean by real-life, production situations. The real question is: should you worry about it before it starts to be a problem? Or a better question: what do you have to do when it starts to be a problem? And if your applications are designed correctly, the answer is:

        shell$ sqlite old-db .dump | psql new-db

        and update

      • > In this light; is SQLLite really any faster than either MySQL or PostgreSQL in real-life, production situations?

        You would never use it for "production situations" when you need an actual RDBMS. SQLite's niche is more like when you need something better than ndbm but not a full blown RDBMS (That said, it actually has more mature SQL support than MySQL). In that respect, it is blazing fast. I have stored a million-row logfile type of database on it and with some simple filter queries, got results li
      • Re:SQLite (Score:3, Interesting)

        by jbolden ( 176878 )
        In this light; is SQLLite really any faster than either MySQL or PostgreSQL in real-life, production situations?

        SQLLite can be as fast as pure data caching to disk for inserts. When you have data coming into the system so fast that a real RDBMS couldn't handle it (on the same hardware) and are willing to have very slow queries until the data is moved over SQLLite rocks. That's a pretty specialized production situation but I had to implement.
    • Repetitive CPU-bound work is a strength of JIT compilation. Java should do fine.

      You want speed out an RDBMS, the deciding factors are likely to be, in decreasing order of importance: good algorithms, well-designed tables and indexes, fast disk IO, abundant RAM.
      • > Repetitive CPU-bound work is a strength of JIT
        > compilation. Java should do fine.

        Right on, the JIT will do the job once the data gets into memory. And if the guys developing the DB backend need to, they can always use the Java NIO packages [sun.com] to make moving data to/from the disks faster. Good times all around.
      • You're quite correct, though the technology you cite is really out of date. JITs, which reduce whole class files to native code, are a brute force technology that were popular when people first discovered the shortcomings of Java bytecode interpreters. JVMs have evolved a bit since then, and usually rely on dynamic compiling, heuristic inlining, and other sophisticated techniques. This not only has a lower overhead than compiling a whole class every time you load it, it's much more effective in creating fas
    • Contrary to popular belief, Java code is almost as fast as code written in C or $COMPILED_LANGUANGE_OF_CHOICE. It actually assembles much of its code in a machine specific state before running, allowing it to run at close the speed of comparable languages.
      • It can run as fast as it wants once it makes it into the CPU. I'm still pretty sure the real reason why Java programs run so slowly on my computer is related to the horrible noises that the disk containing the swapfile makes whenever I try to run a Java program on a computer without a fairly large amount of physical memory.
  • Gotchas (Score:2, Informative)

    by Pan T. Hose ( 707794 )
    This is an interesting question. The databases you ask about don't have MySQL gotchas [sql-info.de], that's for sure. Nor do they have PostgreSQL gotchas [sql-info.de]. They don't have SQLite gotchas [sqlite.org] either. Or Oracle gotchas [google.com], for that matter. But one thing is sure, trust me, they most certainly do have gotchas of their own. Do you know them? Can you work around them? Will they silently corrupt your data? Will it be easy to migrate your data to other RDBMS without changing your applications? How do they scale? Do they fully support SQ [cmu.edu]
    • I was nodding my head in agreement until I got to the very end of your post, and you started listing formal logic topics that are way beyond the scope of day-to-day database design. That kind of rigorous theory is useful for designing a query engine or picking nits with the fine points of various SQL dialects. But I submit that it's serious overkill to insist that every database designer make a serious study of these topics. To really get a useful grasp of these topics, you'd have to do more than read a few
    • I'm going to disagree on that last line as well. I have a PhD in number theory so I understand relational algebray, set theory... I'd say the only thing you really need is one time to have seen that 3rd normal form is the criteria to have table operations be associative and understand what that means. That's a single 1 1/2 hr lecture not a series of courses.
  • How are you supposed to pronounce 'One$DB'?
  • Compiere an open source ERP project typically requires Oracle (although other DBs are supposedly in the works) but now you can also use Daffodil:
    http://daffodildb.com/daffodil-compiere.html/ [daffodildb.com]
    I haven't tried it yet... has anyone else?

God help those who do not help themselves. -- Wilson Mizner

Working...