Hello all,
I was wondering if there is any documentation about the API
for XQuery (i.e., how to write xqueries from a Java
program).
Also, I am interested in using some features of XLink and
XUpdate on top of my XML database. Is support for any of
these in progress?
Thanks in advance,
Alexandra
______________________________________________________
Click here to donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
Hi,
Is there a special reason there are no i686 RPM's anymore like there
were until 4.6.0_rc2?
I think it's a bit weird there are RPM's for the hobby OS 'FedoraCore'
but not for the much used server OS 'RedHat Enterprise 3 (and 4)'?
The FedoraCore (which Core?) needs libstdc++.so.6 whereas RHEL 3 only
has libstdc++.so.5 ...
There also seems to be no SRPM's.
Cheers,
--
Henk van Lingen, Systems & Network Administrator (o- -+
Dept. of Computer Science, Utrecht University. /\ |
phone: +31-30-2535278 v_/_
http://henk.vanlingen.net/http://www.tuxtown.net/netiquette/
Dear MonetDB-users and -developers,
bug reports and especially test script play a crucial role with maintaining
and improving the stability and correct functioning of MonetDB.
However, adding test scripts "a posteriori" as we did recently during the
two "MonetDB-Bug-Days" (a third one is still to come before the end of this
year!) is a very tedious and time-consuming task, especially since who ever
is adding a test script first needs to get familiar with the details of the
very bug report.
Since both the user who submits a bug report and the developer(s) who
take(s) care of fixing a bug are by definition very familiar with the
details of a bug report, it seems more than obvious that they should share
the task of adding a test script to the CVS repository while dealing with
the respective bug, i.e., *before* closing the bug report.
Ideally, the user/submitter provides the query or script that triggers the
bug as well as the expected/correct output with his/her bug report. In case
the user/submitter has CVS check-in privileges, he/she could add the test
script to the CVS repository him-/herself. Otherwise, the developer/assignee
should add the user's test script to the CVS repository. The test script
helps both the developer/assignee and the user/submitter to monitor the
status of the bug by running "Mtest[.py]" (cf.,
http://monetdb.cwi.nl/monet/src/testing/README) or by checking the TestWeb
(http://monetdb.cwi.nl/Development/TestWeb/)
To coordinate this procedure, I made a first draft for a
"MonetDB Bug Etiquette",
which you find attached to this mail.
I'd be very pleased, if you could comment on this.
Thank you all very much for your contribution to make MonetDB even better
than it already is!
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 |
LS,
It is my pleasure to announce that on Nov 19, 2005
around 23:00 GMT we reached the first 10.000 downloads
of MonetDB packages (MonetDB+SQL+XQuery) available on Sourceforge.
Let's go the 100.000 !
regards, Martin
