EoD SQL 1.0 on the way (finally)

After months of hard work (on other projects), I’ve finally turned my attention to EoD SQL once again. The API has been stabilizing the past months with bits of work and attention from a few different people (myself included). There have been a few functionality changes (to correct early mistakes), but on the whole the API has come out with more power, and far better performance than ever before!

The primary things to look out for in the 1.0 release:

  • Control over DataSet caching
    • Array based caching by default
    • NullCache implementation provided
  • DataSet’s stay more connected
    • By making better use of the underlying ResultSet methods, connected DataSet’s almost never disconnect from the database
  • A brand new tutorial that offers a quick and easy path to working with EoD SQL
  • A generally more stable, faster, and much more mature API

The release will probably be made early next week, and will also include a series of new Unit Tests that work with Java DB (included with Java 6). This means that the Unit Tests will now be able to test more of EoD SQL than before.


One Response to “EoD SQL 1.0 on the way (finally)”

  1. Intelligent memory management in Java « Techno Lemming Says:

    […] EoD SQL makes use of WeakReference’s to maintain == (identity) equality. A WeakReference will be valid until the object behind it is garbage collected. The garbage collection can take place as soon as no hard references to the object exist. This is important in EoD SQL, since if the calling code (application or web-app) doesn’t hold a reference to the object, how can it test for any kind of equality? To add to this point, EoD SQL may be dealing with very large volumes of data (since a database ResultSet may be millions of rows long), and holding hard-references may lead to OutOfMemory errors. Holding SoftReferences is also a bad idea, since working through a large ResultSet may lead to performance issues when many threads are working with similar sized ResultSets, and all of them or trying to keep the data in-memory. […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: