Monday, 11 October 2010

Library update

Today's updates are to the PyrrhoLink and OSPLink libraries, to fix a bug in code from 17 Sept.

Friday, 24 September 2010

Adding a Mono version

Today's update includes some version compiled for Linux.

Friday, 10 September 2010

Transaction Profiling

Today's update fixes some mathematical functions that the parser didn't recognise, and makes some improvements to threading.
There is also some new support for transaction profiling, to be discussed in a paper I am writing.

Wednesday, 2 June 2010

Fix to ordering

Today's update fixes a problem with rowset ordering.
Keep me posted on any performance issues.

Monday, 24 May 2010

SQL2008 Compliance

Belatedly perhaps, the version released today has been updated to address SQL2008 compliance. The main change is the new FETCH FIRST n ROWS ONLY clause that can be added in any top-level query expression (usually in combination with an ORDER BY clause).
Please advise me of any performance issues.

Monday, 26 April 2010

Groups and Window Functions

Today's fix is for the advanced window functions.
Email me if you find anything that does not work.

Thursday, 1 April 2010

Java Persistence Library

The Open Source Edition has been updated to fix an error in the Java Persistence implementation org.pyrrhodb.* (PyrrhoJC.jar).
Please report any performance issues to malcolm@pyrrhodb.com .

Monday, 29 March 2010

Fixing Date Types

Today's fixes relate to the date type, which contained some serious errors.
Keep me posted on any performance issues.

Friday, 26 February 2010

Version 4.0 is released

Pyrrho DBMS Version 4.0 is now available. There are three editions, all free to use: Standard, Embedded and OpenSourcePyrrho (OSP). As before, OSP contains an implementation of Java Persistence Architecture v1.0.
The Standard and OSP editions include deployment options for taking advantage of cloud computing technologies, following the design of my December 2009 blog post. There is also an advanced implementation of subtypes as I believe they can be very useful in identifying special features of individual data values (similar to annotations in Excel, or footnotes in documents). I expect this sort of feature in databases to become more important with the increasing interest in provenance and digital curation.
A lot of the code in Version 4.0 is new, so I will be continuing to test this version and updates should get posted regularly. I look forward to receiving feedback on any performance issues and on the concepts introduced in this version.