[Monetdb-developers] [MonetDB-users] Announcement: New Jun2010 feature release of MonetDB suite
It is not June anymore, but nevertheless, the MonetDB team at CWI/MonetDB BV is pleased to announce the Jun2010 feature release of the MonetDB suite of programs. More information (including release notes) on this release is available at http://monetdb.cwi.nl/Development/Releases/Jun2010/. The download location has changed to http://dev.monetdb.org/downloads/. Please fix any bookmarks you may have. -- Sjoerd Mullender
Watch out when upgrading! We just (too late) found a bug that when you upgrade an existing (Feb2010) database to the Jun2010 version, things seem to work OK. But when you then stop and restart the server, things don't work anymore. Our advice: if you have existing databases, DO NOT UPGRADE. See http://bugs.monetdb.org/2573. On 2010-07-01 17:14, Sjoerd Mullender wrote:
It is not June anymore, but nevertheless, the MonetDB team at CWI/MonetDB BV is pleased to announce the Jun2010 feature release of the MonetDB suite of programs.
More information (including release notes) on this release is available at http://monetdb.cwi.nl/Development/Releases/Jun2010/.
The download location has changed to http://dev.monetdb.org/downloads/. Please fix any bookmarks you may have.
-- Sjoerd Mullender
We have decided to retract the Jun2010 release. If you have already upgraded, you should be OK when using new databases. If you have updated with existing databases, and you have already started a server with a pre-existing database, you will probably experience the problems described in the bug mentioned in the quoted text. You can repair your database and make it usable again using the following procedure. This procedure is also described in the Jun2010 release notes. Start the server (again), and connect to it using mclient. Then give the following query to find the id of the 'sys' schema: select id from schemas where name = 'sys'; Make a note of the result. Then give the following 4 queries, replacing the value RESULT with the result obtained in the query above: update _tables set schema_id = RESULT where schema_id not in (select id from schemas) and schema_id <> 0; update functions set schema_id = RESULT where schema_id not in (select id from schemas) and schema_id <> 0; update types set schema_id = RESULT where schema_id not in (select id from schemas) and schema_id <> 0; update sequences set schema_id = RESULT where schema_id not in (select id from schemas) and schema_id <> 0; Stop mclient and, more importantly, the server. Once you restart the server, the database should be usable. However, note that changes to the database schema, especially the creation of tables, functions, types and sequences, will once again make the database unusable (until you repeat the above procedure). We' working on a bug fix release. On 2010-07-02 12:43, Sjoerd Mullender wrote:
Watch out when upgrading!
We just (too late) found a bug that when you upgrade an existing (Feb2010) database to the Jun2010 version, things seem to work OK. But when you then stop and restart the server, things don't work anymore.
Our advice: if you have existing databases, DO NOT UPGRADE.
See http://bugs.monetdb.org/2573.
On 2010-07-01 17:14, Sjoerd Mullender wrote:
It is not June anymore, but nevertheless, the MonetDB team at CWI/MonetDB BV is pleased to announce the Jun2010 feature release of the MonetDB suite of programs.
More information (including release notes) on this release is available at http://monetdb.cwi.nl/Development/Releases/Jun2010/.
The download location has changed to http://dev.monetdb.org/downloads/. Please fix any bookmarks you may have.
------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- Sjoerd Mullender
On Fri, Jul 2, 2010 at 10:43 PM, Sjoerd Mullender
We have decided to retract the Jun2010 release.
Sjoerd, it seems like the June2010 release has been removed from the download site, but no older release has been put there as a replacement. Currently, there seem to be no binary packages available for download. I think it would be a good idea in general to keep older releases around on the download site. There might be reasons why one wants to download one particular outdated release, and I don't think you're that tight on storage space that you have to delete old releases. Warm regards, Jens -- Jens Teubner, jens.teubner@gmail.com
On 08-07-2010 10:06:41 +0200, Jens Teubner wrote:
it seems like the June2010 release has been removed from the download site, but no older release has been put there as a replacement. Currently, there seem to be no binary packages available for download.
I think it would be a good idea in general to keep older releases around on the download site. There might be reasons why one wants to download one particular outdated release, and I don't think you're that tight on storage space that you have to delete old releases.
Why isn't http://dev.monetdb.org/downloads/ sufficient for you? You can find all releases back to 2007 there.
On 2010-07-08 10:06, Jens Teubner wrote:
On Fri, Jul 2, 2010 at 10:43 PM, Sjoerd Mullender
wrote: We have decided to retract the Jun2010 release.
Sjoerd,
it seems like the June2010 release has been removed from the download site, but no older release has been put there as a replacement. Currently, there seem to be no binary packages available for download.
This is only true for Debian/Ubuntu. The Fedora and Windows binaries are there. I'll put the Feb2010-SP2 packages back.
I think it would be a good idea in general to keep older releases around on the download site. There might be reasons why one wants to download one particular outdated release, and I don't think you're that tight on storage space that you have to delete old releases.
The reason this isn't done is that the Debian/Ubuntu tools do not cooperate (or perhaps it is my lack of understanding and willingness to learn). When I install a new package, the old version is automatically removed by the tools. I don't do it on purpose. -- Sjoerd Mullender
participants (3)
-
Fabian Groffen
-
Jens Teubner
-
Sjoerd Mullender