December 2006 - developers-list

Re: [Monetdb-developers] [Monetdb-checkins] MonetDB4/doc - New directory
by Stefan Manegold 22 Dec '06

22 Dec '06

Sjoerd, I suppose, you are only preparing the repository split for now, right? You'll let me/us know before you actually do it, so that we can prepare (i.e., cvs update our checkouts to the latest version before the split, do a final propagation before the split, etc.), right? Thank you very much in advance! Stefan On Fri, Dec 22, 2006 at 08:48:48AM +0000, Sjoerd Mullender wrote: > Update of /cvsroot/monetdb/MonetDB4/doc > In directory sc8-pr-cvs7.sourceforge.net:/tmp/cvs-serv29872/doc > > Log Message: > Directory /cvsroot/monetdb/MonetDB4/doc added to the repository > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > 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 |

2 2

[Monetdb-developers] PHP compilation...
by Romulo Goncalves 21 Dec '06

21 Dec '06

Dear developers, I am compiling M4 with php in windows. I am using the php 5.2.0 The function zend_register_default_exception is defined in : ..\..\..\..\..\..\src\mapi\clients\php\Cimpl\php_monetdb.c as zend_register_default_exception(); but in zend_exceptions.h is defined as: zend_register_default_exception(TSRMLS_D); Can I change it or should it be modified by the responsible of this code ? Regards, Romulo

2 5

Re: [Monetdb-developers] [Monetdb-sql-checkins] sql/NT MSQLserver.bat, 1.7, 1.8
by Romulo Goncalves 21 Dec '06

21 Dec '06

Sjoerd Mullender wrote: > On 2006-12-21 10:32, Fabian Groffen wrote: >> On 20-12-2006 17:56:27 +0100, Sjoerd Mullender wrote: >>>> Why do you start a sql console in M5? In M4 you don't do that either. >>>> (You can't AFAICT.) Maybe it's more consistent if you refrain from >>>> starting an SQL console on the server. >>> This is the script to start a SQL server. Look at the name. It should >>> therefore *start* a SQL service. >> Yes, the SERVICE. Not a console SQL session. > > You're right. I had the same problem, I also thought that I should to sql.start(); > >>> In other words, Romulo, revert your checkin that you did because of >>> Fabian's message. >> Unless this is intended behaviour, yes, otherwise, what is the reason >> behind this? > > As long as the service gets started, I'm ok. Currently in M4, a MIL > console service is started automatically, but we may not need a MAIL > console either. The default language is MAL. So, no MAL console need to be started. I am fixing the Installers, the problem was my m4 compilation failed yesterday because of my python version. Regards, Romulo

1 0

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/modules/pftijah nexi.c, 1.38, 1.39 nexi.h, 1.10, 1.11 nexi_generate_mil.c, 1.18, 1.19 pftijah.mx, 1.67, 1.68
by Stefan Manegold 20 Dec '06

20 Dec '06

On Tue, Dec 19, 2006 at 01:26:44PM +0000, Jan Flokstra wrote: > Update of /cvsroot/monetdb/pathfinder/modules/pftijah > In directory sc8-pr-cvs7.sourceforge.net:/tmp/cvs-serv27367 > > Modified Files: > nexi.c nexi.h nexi_generate_mil.c pftijah.mx > Log Message: > * Synchronization update with Roel, no new features added. > * MMAP problem solved for restarted Mserver? what was the problem? what has been done (tried?) to solve it? 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 |

2 2

[Monetdb-developers] PF: (Failing) algebra tests in the XQuery_0-14 release branch
by Stefan Manegold 18 Dec '06

18 Dec '06

Dear fellow developers, triggered by the discussion in http://sourceforge.net/tracker/index.php?func=detail&aid=1543871&group_id=5… my question: Would anybody mind if we disable all currently failing pathfinder-algebra tests in the XQuery_0-14 release branch? (look for "alg" at http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103… ) Since the algebra version will not officially be supported in the XQuery_0-14 release, the respective problems will not be fixed in the branch, but only in the development trunk. Thanks in advance, 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 |

2 2

[Monetdb-developers] CVS "stable" branch considerations
by Fabian Groffen 14 Dec '06

14 Dec '06

Hi all, A while ago I was discussing the "stable" branch for M5 with Niels, and we came up with the idea to have a "continuous", "configuration free" stable branch, to ease the life of developers/team members that prefer not to live on the (bleeding) edge of novel and exciting technologies. Basically, what the ground idea is, is that when you check out the "stable" branch, that you will always get the latest stable branch. In ASCII-grafix: HEAD o=======================o============================~ \ 1.0 \ 2.0 stable \_______+______+_____ \______+______+______+__ rc_1 rc_2 rc_3 rc_1 rc_2 rc_3 This image is not very different from the current state, but for the 1.0 and the 2.0 release branches, two separate branch names are used: stable-1_0 and stable-2_0. This makes that people who checked out stable-1_0 never get the "next" stable, but instead stay frozen with stable-1_0. The basic idea we had is that people get "upgraded" to the latest stable if they use the "stable" branch, such that they automatically get the latest and greatest, but stable whatever product. For assuring correct tracability a number of tags can be set on the branch, of course. Technically speaking, CVS allows to "force" a branch to be created that already existed, thereby achieving the idea of having a "stable" branch as described above. I'm in favour of such branch, as I think it solves a number of problems with the ever moving branch, and eases CVS use for many of us. It is also easier to remember, as I personally always mix up the captitals, hyphens and underscores. Now we are at the edge of a big CVS move (are we still?), I thought may be it's a good idea to use this strategy for all our modules now. Any thoughts on or complaints against such branch usage?

2 1

[Monetdb-developers] Pegatoo/Gentoo with GCC 4.3
by Fabian Groffen 14 Dec '06

14 Dec '06

Hi all, This is a heads up, that "tonights" testing will be confronted to a GCC 4.3 compiler on Pegatoo, the Gentoo Linux node. GCC 4.3 will most probably be the next compiler that gets stable on Gentoo (like 4.0 was never stable either), hence early testing might be nice. If it results in too many problems, I'll switch it down to GCC 4.2 instead afterwards.

1 0

Re: [Monetdb-developers] [Monetdb-sql-checkins] sql/src/test/leaks/Tests check0.stable.out, 1.1.2.2, 1.1.2.3 check1.stable.out, 1.1.2.2, 1.1.2.3 check2.stable.out, 1.1.2.2, 1.1.2.3 check3.stable.out, 1.1.2.2, 1.1.2.3 check4.stable.out, 1.1.2.1, 1.1.2.2 check5.stable.out, 1.1.2.1, 1.1.2.2
by Martin Kersten 13 Dec '06

13 Dec '06

ziek ?:-) of alleen teveeel gedanst.

2 1

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/runtime pathfinder.mx,
by p.a.boncz＠chello.nl 13 Dec '06

13 Dec '06

Hoi Sjoerd, In de log message ben ik denk ik vergeten om op te schrijven dat ik consecutive text node coalescing uit had gezegd; daarentegen heb ik je een uitgebreide email geschreven waarin ik dit verteld heb dat en waarom ik dat gedaan heb. De fix_consecutive_text code heeft een groot performance probleem. Het maakt in feite deletes onbruikbaar. Op de 1GB document test heb ik hem na enige minuten afgebroken. Omdat ik niet wist hoe die code sneller gemaakt kan worden heb ik het uitgezet. Hoewel technisch niet correct, is het voor weinig applicaties een ramp als er twee text nodes na elkaar komen. De pathfinder gegenereerde code breekt daar niet van, voor zover ik weet. Maar ik begrijp dat jij het hier niet mee eens bent.. Het beste zou zijn om fix-consecutive text te beperken tot de range van nodes direct om het delete punt heen. Dan zou performance geen probleem hoeven te zijn. Wat ik zag was dat er een CTrefine over het hele document heen ging. Peter > > van: Sjoerd Mullender <sjoerd(a)acm.org> > datum: 2006/12/12 Tue PM 04:11:49 CET > aan: monetdb-developers(a)lists.sourceforge.net > cc: monetdb-pf-checkins(a)lists.sourceforge.net > onderwerp: Re: [Monetdb-pf-checkins] pathfinder/runtime pathfinder.mx, > 1.269.2.14, 1.269.2.15 pf_support.mx, 1.172.2.11, 1.172.2.12 > >

2 1

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/runtime pathfinder.mx, 1.269.2.14, 1.269.2.15 pf_support.mx, 1.172.2.11, 1.172.2.12
by Sjoerd Mullender 12 Dec '06

12 Dec '06

On 2006-12-09 16:19, Peter Boncz wrote: > Update of /cvsroot/monetdb/pathfinder/runtime > In directory sc8-pr-cvs7.sourceforge.net:/tmp/cvs-serv28149 > > Modified Files: > Tag: XQuery_0-14 > pathfinder.mx pf_support.mx > Log Message: > various performance fixes; small inserts and deletes are now reasonably fast > > - index new qnames in qnloc index > - better handling of the hash tables on the qn_loc index > - shortened the collection lock time by moving most of the logging > out of the critical period > > > > Index: pf_support.mx > =================================================================== > RCS file: /cvsroot/monetdb/pathfinder/runtime/pf_support.mx,v > retrieving revision 1.172.2.11 > retrieving revision 1.172.2.12 > diff -u -d -r1.172.2.11 -r1.172.2.12 > --- pf_support.mx 8 Dec 2006 17:48:43 -0000 1.172.2.11 > +++ pf_support.mx 9 Dec 2006 15:19:52 -0000 1.172.2.12 > @@ -2096,47 +2097,22 @@ > } > > var texts := ws.fetch(UPDATED_TEXT); > - fix_consecutive_texts(ws, texts); > + #fix_consecutive_texts(ws, texts); > > # get containers in the order in which we must commit them ([COLL_ID,CONT]) > var cont_order := affected_conts.reverse().mirror().leftfetchjoin(ws.fetch(CONT_COLL)).reverse().sort(); > 1. what does this change have to do with the log message? 2. this change breaks the document: if a node between two text nodes is deleted, the two text nodes have to be coalesced. That is what this function does. It is a necessary step to keep subsequent queries working correctly. -- Sjoerd Mullender

1 0