Difference between revisions of "Talk:RoboResearch"

From Robowiki
Jump to navigation Jump to search
(Java DB)
Line 5: Line 5:
 
== HSQLDB No More ==
 
== HSQLDB No More ==
  
Beware of abrupt shutdowns of the database server.  I just lost all my scores since 0073 (currently on 0083), apparently because I closed Eclipse which simply killed the database process, instead of shutting it down nicely.  I certainly thought it would handle such things better than that, and I have done it many times before with no consequence, but apparently my timing was bad this time.  Does anyone have a good recommendation for a more reliable database that can be run without firing off a separate process, if desired? --[[User:Simonton|Simonton]] 07:51, 18 September 2008 (UTC)
+
Beware of abrupt shutdowns of the database server.  I just lost all my scores between [[Simonton/PFResearch]] 0073 and 0083, apparently because I closed Eclipse which simply killed the database process, instead of shutting it down nicely.  I certainly thought it would handle such things better than that, and I have done it many times before with no consequence, but apparently my timing was bad this time.  Does anyone have a good recommendation for a more reliable database that can be run without firing off a separate process, if desired? --[[User:Simonton|Simonton]] 07:51, 18 September 2008 (UTC)
 +
 
 +
It looks like the Apache Derby implementation distributed with Java 6 would be the natural choice!  Expect that change to come in the near future, for fear of losing more of my data otherwise!  --[[User:192.88.212.34|192.88.212.34]] 15:04, 18 September 2008 (UTC)

Revision as of 17:04, 18 September 2008

SVN Update Notes

If you update from SVN, be ready to change your .cfg files. The example "run.cfg" is updated - it's still easy. Perhaps easier than they were! --Simonton 04:25, 16 September 2008 (UTC)

HSQLDB No More

Beware of abrupt shutdowns of the database server. I just lost all my scores between Simonton/PFResearch 0073 and 0083, apparently because I closed Eclipse which simply killed the database process, instead of shutting it down nicely. I certainly thought it would handle such things better than that, and I have done it many times before with no consequence, but apparently my timing was bad this time. Does anyone have a good recommendation for a more reliable database that can be run without firing off a separate process, if desired? --Simonton 07:51, 18 September 2008 (UTC)

It looks like the Apache Derby implementation distributed with Java 6 would be the natural choice! Expect that change to come in the near future, for fear of losing more of my data otherwise! --192.88.212.34 15:04, 18 September 2008 (UTC)