Darn, just when I decided to announce my port of the monetdb-ruby-sql
gem to xquery, you release a fix of your own :P Anyway it's here:
http://github.com/d-snp/ruby-monetdb-xquery
There's still some differences between the official one and mine, I
think mine handles errors a bit more gracefully, but it could be I
missed something. I will look at the other changes as soon as possible
to see if mine has any odd behaviour.
In the following weeks I will be working on making XQuery and MonetDB
work on DataMapper (since DataMapper is a nicer framework than
ActiveRecord, and also ActiveRecord depends heavily on SQL) If anyone
has any comments on this or any questions or would like to help out
then please let me hear. I plan on putting the datamapper
implementation on github too somewhere this week.
Kind regards,
Tinco Andringa
On Thu, Nov 12, 2009 at 09:06:23AM +0000, Fabian wrote:
> Update of /cvsroot/monetdb/MonetDB
> In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv25980
>
> Modified Files:
> Tag: Nov2009
> configure.ag
> Log Message:
> Yippy yay for messing with this at this stage of the development cycle... Revert my yesterday's commit here as it not only breaks compilation on OSX 10.6 (the original problem), but also Solaris 10. We need to facilitate people doing cross-compilation in some other way.
Might simply using AC_CHECK_FUNCS(fdatasync) be an option, here?
Stefan
> Index: configure.ag
> ===================================================================
> RCS file: /cvsroot/monetdb/MonetDB/configure.ag,v
> retrieving revision 1.208.2.2
> retrieving revision 1.208.2.3
> diff -u -d -r1.208.2.2 -r1.208.2.3
> --- configure.ag 11 Nov 2009 11:17:52 -0000 1.208.2.2
> +++ configure.ag 12 Nov 2009 09:06:21 -0000 1.208.2.3
> @@ -94,17 +94,15 @@
>
> # Checks for library functions.
>
> -# OSX 10.6 (Snow Leopard) somehow makes configure believe that fdatasync
> -# exists, in reality however, it does not on this platform.
> -AC_CACHE_CHECK([for fdatasync],[ac_cv_func_fdatasync],[
> - AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[
> +# Fix for OSX 10.6 (Snow Leopard) stolen from:
> +# http://blogs.sun.com/elambert/entry/drizzle_in_the_snow_how
> +AC_RUN_IFELSE([AC_LANG_PROGRAM([[
> #include <unistd.h>
> ]],[[
> fdatasync(4);
> ]])],
> [ac_cv_func_fdatasync=yes],
> [ac_cv_func_fdatasync=no])
> -])
> AS_IF([test "x${ac_cv_func_fdatasync}" = "xyes"],
> [AC_DEFINE([HAVE_FDATASYNC],[1],[If the system has a working fdatasync])])
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Monetdb-checkins mailing list
> Monetdb-checkins(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monetdb-checkins
>
>
--
| Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl |
| CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ |
| 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 |
| The Netherlands | Fax : +31 (20) 592-4312 |
Dear all,
The MonetDB team at CWI/MonetDB BV are pleased to announce the new
"Nov2009" feature release of the MonetDB suite of programs.
This feature release is backward compatible with the previous
releases (Nov2008 through Aug2009-SP2).
Caveat 1:
In MonetDB/XQuery, we extended and improved the use of value indices on
comparisions between a value and an XPath ending in text() or attribute
access (e.g., doc(x)//x/y[z/text() = "foo"] and for $x in doc//x/y where
$x/@z = "bar" return $x); such queries do not need scanning data, but start
at the index and navigate backwards from there.
This required a change in the physical database storage. While the Nov2009
release of MonetDB/XQuery can still read older (pre-Nov2009) databases, it
is recommended to (back-up and) re-shred all documents to benefit from the
new indices and achieve optimal performance.
Caveat 2:
When upgrading from a release older than May2009 (i.e., Nov2008
through Feb2009-SP2), you need to move your write-ahead log
following the "recommended" instructions for
SQL (<http://monetdb.cwi.nl/Development/Releases/May2009/#SQL>)
and/or
XQuery (<http://monetdb.cwi.nl/Development/Releases/May2009/#XQuery>).
More information on the new release is available at
<http://monetdb.cwi.nl/Development/Releases/Nov2009/>.
The sources and binaries are available at
<http://monetdb.cwi.nl/Download/>.
Enjoy!
The MonetDB team at CWI/MonetDB BV.
--
| Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl |
| CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ |
| 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 |
| The Netherlands | Fax : +31 (20) 592-4312 |
Hello Developers,
Usually I try to report bugs (and try to find the worst of the
system), but just this morning I noticed my mserver5 instance
(Aug2009), which I have been intensively querying over the last days
with ten-thousands of reasonably complex queries and sometimes with
more than 20 queries in parallel. It just passed the 4800 minutes of
actual cpu time (= 80 hours of hard work) and still going strong. I
thought it was worth mentioning!
Cheers,
Wouter
p.s. roberto, actually it's your mserver instance...
On 2009-11-20 15:55, Fabian wrote:
> Update of /cvsroot/monetdb/testing/src
> In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv28457
>
> Added Files:
> quicktest
> Log Message:
> Time to show what I'm hiding. (Also nice to finally get revision control)
>
> My efforts of the last few days resulted in this initial version of
> "quicktest", the not-even-close-to-Mtest.py fast mtest emulator.
>
> Basically it started all out of frustration of not being able to
> implement many ideas in Mtest.py, so I decided to see how far I'd come
> by rewriting from scratch (incidentially also in a language I actually
> can read and understand).
Are you also going to port this to Windows? There is a reason to use
Python, you know.
--
Sjoerd Mullender
On Nov 15, 2009, at 14:59 , Stefan Manegold wrote:
> Update of /cvsroot/monetdb/pathfinder/runtime/xrpc/admin/Tests
> In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv15431
>
> Modified Files:
> Tag: Nov2009
> All
> Log Message:
>
> conditionally disabled backup_restore_noxrpc test
> for Algebra, as it required fn:put,
> which it not (yet?) available for Algebra;
> please re-enable once fn:put becomes available
> also with Algebra
>
> ps:
> does this also means that since XRPC and module
> queries not longer automatically fall back to MPS,
> the XRPC-/module-based administrative console
> does no longer offer all its functionallity
> when server by a default ALG MonetDB/XQuery?
The intension is to disable automatic fall back to MPS *only* for module queries.
This does not apply to XPRC queries (incl. the admin functions), which should thus still be available in ALG.
> Index: All
> ===================================================================
> RCS file: /cvsroot/monetdb/pathfinder/runtime/xrpc/admin/Tests/All,v
> retrieving revision 1.3.10.1
> retrieving revision 1.3.10.2
> diff -u -d -r1.3.10.1 -r1.3.10.2
> --- All 24 Oct 2009 15:07:19 -0000 1.3.10.1
> +++ All 15 Nov 2009 13:58:58 -0000 1.3.10.2
> @@ -1,6 +1,7 @@
> add_del_doc_noxrpc
> NOT_ALGEBRA?add_del_doc
> -backup_restore_noxrpc
> +# fn:put()
> +NOT_ALGEBRA?backup_restore_noxrpc
> NOT_ALGEBRA?backup_restore
> # pf:mil()
> NOT_ALGEBRA?db_stats_noxrpc
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Monetdb-pf-checkins mailing list
> Monetdb-pf-checkins(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monetdb-pf-checkins
Dear all,
lacking the time to constantly check each bug report and each failing test,
I'll as of now leave it to the resposibility of
- bug report submitters and
- developers that fix and close bugs, as well as
- those that develope new code and get detailed TestWeb emails about the
consequences of their changes,
to ensure that
- each failing test is documented in a bug report, and
- each closed (fixed) bug report is backed-up by a test in CVS to monitor
the status of that very query or usage scenario.
Thank you for understanding my decision and for helping us all to maintain
and improve the stability, correctness and quality of the MonetDB code base.
Kind regards,
Stefan
--
| Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl |
| CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ |
| 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 |
| The Netherlands | Fax : +31 (20) 592-4312 |