Thursday, May 1, 2008

EnterpriseDb -- the real open source database

According to ads displayed with my email, Enterprise DB is the real open-source database. At first, I thought that the source for most of their features was not available (I have no interest in Oracle compatability, so I don't want to see that code). But it is available at the download page.

I think that PostgreSQL is amazing for its technology, community, code (nice formatting and documentation) and environment that allows many companies to create value-added versions of it and eventually push back some of those changes to the community. The talk at the MySQL Conference was also amazing, but I had to miss it.

EnterpriseDb has published the source for gridsql that can run queries in parallel on a cluster. Who wants to do a MySQL port?

4 comments:

  1. Mark,

    The source code for Postgres Plus is all there for you. Go to: http://www.enterprisedb.com/products/download.do

    At the bottom, the component source code shows all of the different pieces that make up Postgres Plus. This includes the base PostgreSQL database, plus all of the other components that EnterpriseDB has tested and integrated into the product. For example, Migration Studio, GridSQL, PLpgSQL Debugger and more.

    I hope this helps you!

    Derek
    EnterpriseDB

    ReplyDelete
  2. Thanks. I misunderstood the bundling. gridsql looks great and almost makes me want to use Java again. I am curious how many PostgreSQL dependencies are in there.

    ReplyDelete
  3. Mark,

    While it has been fully optimized for Postgres, it is able to be used with other databases as well. ;)

    Derek

    ReplyDelete
  4. Hi Mark,

    Actually there really is no need to "port" GridSQL if you want to get it up and running and do not need every MySQL command and syntax variation. There are many flexible configuration options that allow you to tell GridSQL about the underlying database. Properly configured, it runs fine against MySQL (or other databases). It is just targeted for PostgreSQL, as Derek mentioned.

    Rather than fork the code for any MySQL specific development, it would make more sense to contribute code back to the same source base to take advantage of ongoing development enhancements.

    Regards,

    Mason

    ReplyDelete

 
Creative Commons License
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License.