June 2006 - users-list

[MonetDB-users] XQuery API and XLink/XUpdate support
by Alexandra Mart�nez 27 Jun '24

27 Jun '24

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/

4 3

[MonetDB-users] MonetDB 4.12.0 Release Announcement
by Fabian Groffen 23 Jun '06

23 Jun '06

It is my great pleasure to announce the availability of MonetDB 4.12.0 and its accompanying SQL 2.12.0 and XQuery 0.12.0. This release is the next step in delivering the high performance database system that has been under development for several years now. Some of the many changes since the 4.10.2 release include: MonetDB/XQuery 0.12.0 (nick-named "Ceres") Various improvments of functionality and performance. Addition of XPath extensions for XML standoff annotations. "Ceres" is a small detour on our trip to "Mars" [1], as update functionality is unfortunately still not robust enough for consumption by the majority. MonetDB/SQL 2.12.0 Many bugfixes. Support for local and global temporary tables. Preliminary support for triggers. For a complete list of new features and known problems, please see the release notes and errata list, available at: http://monetdb.cwi.nl/Development/Roadmap/Version4.12/index.html MonetDB/Five Alpha Release 1 ============================ The efforts on the next generation of MonetDB, version Five, are released now. This snapshot of version Five of MonetDB is the very first alpha release of this ongoing development. Beware: alpha is alpha! This software is only suitable as sneak-preview into the MonetDB developers team's kitchen! Come and taste some of the many delicious spices we prepare. Unlike the previous generation, Five comes with the MAL language, instead of MIL, which makes it completely incompatible with old MIL scripts. However, the SQL sources work fine with this alpha release. Comparing the performance of both backends via SQL should give you an indication of what our cooks will serve for dinner. This first alpha "appetiser" release of MonetDB/Five is nick-named "Tomato Soup". Interested users are invited to visit our MonetDB/Five page for more details: http://monetdb.cwi.nl/Development/Five/index.html Availability ============ The MonetDB family products are supported on i686, x86_64 and ia64 Linux, i686 Solaris 10, ppc and ppc64 Mac OS X 10.4 and i686 Windows XP. Binary distributions are available for Linux and Windows. The new release is available for download from our SourceForge page: http://sourceforge.net/project/showfiles.php?group_id=56967 Acknowledgements ================ Many man-hours were donated by various people to make this release happening. I want to thank al MonetDB developers for their efforts spent into this piece of software. All of our contributors and bug reporters also deserve the credits for the time they put into their contribution. Further Information =================== Further information about MonetDB, MonetDB/SQL and MonetDB/XQuery is available on our web site at: http://monetdb.cwi.nl/ http://monetdb.cwi.nl/SQL/ http://monetdb.cwi.nl/XQuery/ For details about recent changes, migration from earlier versions, and future plans, please visit our roadmap page: http://monetdb.cwi.nl/Development/Roadmap/ User CVS Information ==================== If you use a CVS checkout, you might have to change some things in order to keep on working with the latest sources. With every release some new tags are set and numbers changed. Please check your source trees that you use the right sticky tags on them. The sources that are put in this release are tagged as follows: MonetDB MonetDB_4-12-0 sql SQL_2-12-0 pathfinder XQuery_0-12-0 The new stable branches are now available through the following tags: MonetDB MonetDB_4-12 sql SQL_2-12 pathfinder XQuery_0-12 To update to the new stable branches use ``cvs update -r <branch tag>`` for the repositories you work with. Feedback or Questions ===================== If you have any questions or feedback regarding this release, feel free to contact us through this list: monetdb-users(a)lists.sourceforge.net We hope you will enjoy this new release of MonetDB as much as we do. [1] See http://en.wikipedia.org/wiki/1_Ceres and http://www.nasa.gov/multimedia/imagegallery/image_feature_404.html

1 0

Re: [MonetDB-users] Reminder: MonetDB Bug-Etiquette
by Stefan Manegold 19 Jun '06

19 Jun '06

Dear all, two more small pleas that will make bug reporting and fixing much simpler and smoother: - When submitting a bug, please *always* set both the "Category:" and the "Group:"! This helps the developer(s) to identify which version/part of the system your bug occured with. - When changing the "Status:", "Resolution:", and/or "Priority:", please *always* provide a comment that explans the motivation and/or reason for your action. E.g., when closing a bug report, please mention whether, how and where you fixed it. Thanks again! Stefan On Sun, Jun 18, 2006 at 10:09:13PM +0200, Stefan Manegold wrote: > Dear all, > > since the last MonetDB "BugDay" on Dec 19 2005, many bugs have been reported > and fixed. > > Unfortunately, not all bug reports that have been closed since then have > been backed-up by a test script in CVS to verify and monitor to validity of > the respective bug fix, as described in the "MonetDB Bug-Etiquette" > (cf. one of > http://sourceforge.net/mailarchive/forum.php?thread_id=9021727&forum_id=398… > http://sourceforge.net/mailarchive/forum.php?thread_id=9021726&forum_id=425… > ) > > According to the "MonetDB Bug-Etiquette", a bug report should (may/must) not > be closed without adding a respective test to our test system in CVS. > > While both the user/submitter that reports the bug and the > developer/assignee that fixes it should share the task of "designing" the > test and adding it to the test system in CVS, we agreed that the > developer/assignee is finally "responsible" that the test is indeed added > *before* the bug report is closed. > > > To ensure the stability and correctness of MonetDB and its companions and to > avoid that supposedly fixed bug sneak in again unnoticed, I'd like to ask > all of you that reported and/or fix any bug(s) since Dec 19 2005 > the following favour: > > Please check all "your" bugs (see * below) since Dec 19 2005, whether a test > has been added or not. > + If the comments in the bug report are not clear, please check the CVS > repository. > + If you're a user/submitter and don't know where to look or what to do, > please remind the respective developer/assignee of your bug by added a > respective comment and re-opening the bug report. > + If there is a test, or no test is necessary or feasible, but the > bug-report does not mention this clearly, please add a new comment that > explains the situation. > + If there is no test although there should be one, please re-open the bug > report with a respective comment to indicate that a test must be added. > As said before, "users/submitters" are welcome to help adding tests, but > developers/assignees are finally responsible that the tests are indeed > added. > > Please recall, we plan to release MonetDB 4.12, MonetDB/SQL 2.12 and > MonetDB/XQuery 0.12 soon (i.e., before the end of this month), > and we all want them to be as stable and "bug-free" as possible...! > > > Feel free to use these channels to comment and/or ask questions. > > > Thank you all very much for your contributions to make MonetDB even better > than it already is! > > > Kind regards, > > Stefan > > > *) To find "your" bugs, just > - go to http://sourceforge.net/tracker/?group_id=56967&atid=482468 , > - select your username from the list "Assignee:", > - or enter your username as "Submitter username (show mine):" > (and set "Assignee:" to "Any"), > - set "Status:", "Category:" & "Group:" to "Any", > - set "Sort By:" to "Open Date" and "Descending", > - and click on "Browse". > > -- > | 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 | -- | 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 |

1 0

[MonetDB-users] Reminder: MonetDB Bug-Etiquette
by Stefan Manegold 18 Jun '06

18 Jun '06

Dear all, since the last MonetDB "BugDay" on Dec 19 2005, many bugs have been reported and fixed. Unfortunately, not all bug reports that have been closed since then have been backed-up by a test script in CVS to verify and monitor to validity of the respective bug fix, as described in the "MonetDB Bug-Etiquette" (cf. one of http://sourceforge.net/mailarchive/forum.php?thread_id=9021727&forum_id=398… http://sourceforge.net/mailarchive/forum.php?thread_id=9021726&forum_id=425… ) According to the "MonetDB Bug-Etiquette", a bug report should (may/must) not be closed without adding a respective test to our test system in CVS. While both the user/submitter that reports the bug and the developer/assignee that fixes it should share the task of "designing" the test and adding it to the test system in CVS, we agreed that the developer/assignee is finally "responsible" that the test is indeed added *before* the bug report is closed. To ensure the stability and correctness of MonetDB and its companions and to avoid that supposedly fixed bug sneak in again unnoticed, I'd like to ask all of you that reported and/or fix any bug(s) since Dec 19 2005 the following favour: Please check all "your" bugs (see * below) since Dec 19 2005, whether a test has been added or not. + If the comments in the bug report are not clear, please check the CVS repository. + If you're a user/submitter and don't know where to look or what to do, please remind the respective developer/assignee of your bug by added a respective comment and re-opening the bug report. + If there is a test, or no test is necessary or feasible, but the bug-report does not mention this clearly, please add a new comment that explains the situation. + If there is no test although there should be one, please re-open the bug report with a respective comment to indicate that a test must be added. As said before, "users/submitters" are welcome to help adding tests, but developers/assignees are finally responsible that the tests are indeed added. Please recall, we plan to release MonetDB 4.12, MonetDB/SQL 2.12 and MonetDB/XQuery 0.12 soon (i.e., before the end of this month), and we all want them to be as stable and "bug-free" as possible...! Feel free to use these channels to comment and/or ask questions. Thank you all very much for your contributions to make MonetDB even better than it already is! Kind regards, Stefan *) To find "your" bugs, just - go to http://sourceforge.net/tracker/?group_id=56967&atid=482468 , - select your username from the list "Assignee:", - or enter your username as "Submitter username (show mine):" (and set "Assignee:" to "Any"), - set "Status:", "Category:" & "Group:" to "Any", - set "Sort By:" to "Open Date" and "Descending", - and click on "Browse". -- | 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 |

1 0

[MonetDB-users] join on 2 attributes
by Henning Rode 07 Jun '06

07 Jun '06

hej monet-db-useres, i maybe forgot a very basic thing here, but how do you perform in monet an equi-join on two attributes. it seems such a normal task that there must be something easier than what i did now (see attachment: generating first example instances, then do the join with 'intersect') you should have the same problem when you select on a qname (namespace and tagname), but i could not find that example. if i underspecified my problem, just let me know in advance ;-) best -henning var x_a := new(void,int).seqbase(0@0); x_a.append(1); x_a.append(1); x_a.append(1); x_a.append(2); x_a.append(2); x_a.append(2); x_a := [oid](x_a); var x_b := new(void,int).seqbase(0@0); x_b.append(1); x_b.append(2); x_b.append(4); x_b.append(1); x_b.append(2); x_b.append(4); x_b := [oid](x_b); var y_c := new(void,int).seqbase(0@0); y_c.append(1); y_c.append(2); y_c := [oid](y_c); var y_d := new(void,int).seqbase(0@0); y_d.append(2); y_d.append(1); y_d := [oid](y_d); print(x_a,x_b); print(y_c,y_d); var x_y := join(x_a,y_c.reverse()); var x_d := join(x_y,y_d); intersect(x_b,x_d).print();

1 0

[MonetDB-users] MEL Question: Creating a New Search Accelerator
by John Cieslewicz 05 Jun '06

05 Jun '06

I am trying to build a new search accelerator as described in Section 2.5 of the Monet Extension Language (MEL) User Guide (http://monetdb.cwi.nl/TechDocs/Core/mel/index.html) When I execute mel on my module definition it does not seem to recognize the ".ACCELERATOR" key word. In Section 3.5, "Implementing Accelerators" the 'mean' accelerator implementation is described. Is there an example of the module definition of 'mean' in MEL? I also looked at the mel source code and found that in buildtools/_MEL/mel.yy it appears that 'accelerator' is not part of the grammar for a module: ---- definition: atomdef | command | iterator | builtin | operator | object | MEL_PRELUDE '=' ident ';' { $$.sym = new Prelude(MEL_PRELUDE, $3.s); } | MEL_EPILOGUE '=' ident ';' { $$.sym = new Epilogue(MEL_EPILOGUE, $3.s); } ; --- Questions: (1) Are user defined search accelerator modules actually supported in MonetDB? (2) If so, is there an example of such an accelerator module? (3) If not, what would be the best way to integrate a new index technique into the system? Thanks! -John

1 0