- developers-list - monetdb.org

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/src/tools/java/src/nl/cwi/monetdb/xquery/util CmdLineOpts.java, XQuery_0-20, NONE, 1.1.2.1 OptionsException.java, XQuery_0-20, NONE, 1.1.2.1
by Fabian Groffen 10 Oct '07

10 Oct '07

On 10-10-2007 11:01:20 +0000, Ying Zhang wrote: > Update of /cvsroot/monetdb/pathfinder/src/tools/java/src/nl/cwi/monetdb/xquery/util > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv8103/src/tools/java/src/nl/cwi/monetdb/xquery/util > > Added Files: > Tag: XQuery_0-20 > CmdLineOpts.java OptionsException.java > Log Message: > Moved the XRPC Wrapper stuff into pathfinder/src/tools/java, because > XRPC Wrapper is not a client program and it is XQuery related. > > The XRPC Wrapper is build in a separate RPM package > (MonetDB4-XQuery-xrpcwrapper), so that the > pathfinder package is still Java-independent. Please note that this is code replication. (which IMHO is BAD).

2 3

Re: [Monetdb-developers] [Monetdb-checkins] MonetDB/NT monetdb_winconfig.h, , 1.2, 1.3
by Niels Nes 10 Oct '07

10 Oct '07

On Wed, Oct 10, 2007 at 09:05:45AM +0000, Romulo Goncalves wrote: > Update of /cvsroot/monetdb/MonetDB/NT > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv14659 > > Modified Files: > monetdb_winconfig.h > Log Message: > Move the definition of ssize_t as int into the win32 else clause > Please check if it is correct like this. The compilation works, but it gives warnnings > about probable lost of data witht the convertion from ssize_t to BUN. Shouldn't this also be done on the stable? The move of the line is fine. BUN in cvs head is still a 'size_t' (same as oid), ie ssize_t (signed) indeed may lose info. Niels > > > Index: monetdb_winconfig.h > =================================================================== > RCS file: /cvsroot/monetdb/MonetDB/NT/monetdb_winconfig.h,v > retrieving revision 1.2 > retrieving revision 1.3 > diff -u -d -r1.2 -r1.3 > --- monetdb_winconfig.h 3 Oct 2007 13:59:59 -0000 1.2 > +++ monetdb_winconfig.h 10 Oct 2007 09:05:43 -0000 1.3 > @@ -668,13 +668,14 @@ > > /* The size of a `void *', as computed by sizeof. */ > #define SIZEOF_VOID_P 4 > -#endif > + > > /* The size of a `ssize_t', as computed by sizeof. */ > #define SIZEOF_SSIZE_T SIZEOF_SIZE_T > typedef int ssize_t; > #define HAVE_SSIZE_T 1 > > +#endif > /* The size of a `__int64', as computed by sizeof. */ > #define SIZEOF___INT64 8 > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Monetdb-checkins mailing list > Monetdb-checkins(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-checkins -- Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes(a)cwi.nl

3 2

[Monetdb-developers] Object persistence using MonetDB
by darabi＠web.de 10 Oct '07

10 Oct '07

Hello, I'm a developer located in Germany with a current interest in object persistence for a dynamically typed language. I was experimenting with something along the lines of the decomposed storage model when I found out that it was (of course) decades old and found the papers about it and MonetDB. Many thanks for your efforts and for this great piece of software. I was reading the 1995 CWI report 'High Performance support for OO traversals in monet' and was wondering whether the ideas in it are still present in today's MonetDB. And if not, how much effort would it take to implement OO persistence using MAL. I would also appreciate any pointer to papers, code samples etc. in this direction. If I understand correctly, in the beginning, MonetDB was rather heading towards a OODBMS. Was there any reason why you didn't pursue that goal? Is there any road block? Thank you very much for your help. Kambiz Darabi

1 0

Re: [Monetdb-developers] [Monetdb-checkins] MonetDB5/src/compiler/Tests mal01.stable.out, , 1.1, 1.2 sql01.mal, , 1.1, 1.2 sql01.stable.out, , 1.1, 1.2
by Stefan Manegold 09 Oct '07

09 Oct '07

On Tue, Oct 09, 2007 at 08:09:05PM +0000, Martin Kersten wrote: > Update of /cvsroot/monetdb/MonetDB5/src/compiler/Tests > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv28543/Tests > > Modified Files: > mal01.stable.out sql01.mal sql01.stable.out > Log Message: > Make the test self-contained, i.e. not dependent on sql libraries. Just as a double-check: Are the warnings below expected/correct, and hence their approval intended? Stefan > Index: mal01.stable.out > =================================================================== > RCS file: /cvsroot/monetdb/MonetDB5/src/compiler/Tests/mal01.stable.out,v > retrieving revision 1.1 > retrieving revision 1.2 > diff -u -d -r1.1 -r1.2 > --- mal01.stable.out 7 Oct 2007 06:44:53 -0000 1.1 > +++ mal01.stable.out 9 Oct 2007 20:09:01 -0000 1.2 [...] > +!WARNING: call to bat.new can not be handled correctly [...] > > Index: sql01.stable.out > =================================================================== > RCS file: /cvsroot/monetdb/MonetDB5/src/compiler/Tests/sql01.stable.out,v > retrieving revision 1.1 > retrieving revision 1.2 > diff -u -d -r1.1 -r1.2 > --- sql01.stable.out 7 Oct 2007 06:44:55 -0000 1.1 > +++ sql01.stable.out 9 Oct 2007 20:09:02 -0000 1.2 > +MCdynamicCompiler: sql.qry > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly > +!WARNING: call to sql.bind can not be handled correctly [...] -- | 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 1

Re: [Monetdb-developers] [Monetdb-checkins] MonetDB5/src/compiler/Tests All, , NONE, 1.1 mal01.mal, , NONE, 1.1 mal01.stable.err, , NONE, 1.1 mal01.stable.out, , NONE, 1.1 sql01.mal, , NONE, 1.1 sql01.stable.err, , NONE, 1.1 sql01.stable.out, , NONE, 1.1
by Stefan Manegold 09 Oct '07

09 Oct '07

On Sun, Oct 07, 2007 at 06:44:57AM +0000, Martin Kersten wrote: > Update of /cvsroot/monetdb/MonetDB5/src/compiler/Tests > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv1743/Tests > > Added Files: > All mal01.mal mal01.stable.err mal01.stable.out sql01.mal > sql01.stable.err sql01.stable.out > Log Message: > Patching some very old code to bring it closer to reality. > The examples roughly indicate the code to be considered for inclusion > in a compiled plan. The expected gain is only 25-50% interpreter overhead, > which result from known argument locations and stack initialization actions. > A real optimizing MAL ->C compiler should weave instructions to > more efficient ones, e.g. dropping intermediates. > > The SQL version highlights, however, the calls needed against the BBP > due to the shared bat assumption. > > [...] > --- NEW FILE: sql01.mal --- > include sql; ^^^ This test is bound to fail here (i.e., in MonetDB5) as there is no module "sql" in MonetDB5; module "sql" is only provided by sql. Stefan > #sql.compiler("sql01","select * from tables;"); > include mal_compiler; > function user.qry():void; > T1:bat[:oid,:int]{notnil=true,rows=0:lng,bid=113} := sql.bind("tmp","Ttables","id",0); > constraints.emptySet(T1); > T10:bat[:oid,:sht]{notnil=true,rows=0:lng,bid=117} := sql.bind("tmp","Ttables","type",0); > T13:bat[:oid,:int]{notnil=true,rows=30:lng,bid=67} := sql.bind("sys","Ttables","id",0); > T15:bat[:oid,:int]{notnil=true,rows=0:lng,bid=307} := sql.bind("sys","Ttables","id",1); > constraints.emptySet(T15); > T15:bat[:oid,:int]{notnil=true,rows=0:lng,bid=307} := nil; > T16:bat[:oid,:int]{notnil=true,rows=0:lng,bid=309} := sql.bind("sys","Ttables","id",2); > constraints.emptySet(T16); > T16:bat[:oid,:int]{notnil=true,rows=0:lng,bid=309} := nil; > T20:bat[:oid,:sht]{notnil=true,rows=30:lng,bid=71} := sql.bind("sys","Ttables","type",0); > T39:bat[:oid,:str]{notnil=true,rows=0:lng,bid=114} := sql.bind("tmp","Ttables","name",0); > T42:bat[:oid,:str]{notnil=true,rows=30:lng,bid=68} := sql.bind("sys","Ttables","name",0); > T47:bat[:oid,:int]{notnil=true,rows=0:lng,bid=115} := sql.bind("tmp","Ttables","schemaTid",0); > T50:bat[:oid,:int]{notnil=true,rows=30:lng,bid=69} := sql.bind("sys","Ttables","schemaTid",0); > T55:bat[:oid,:str]{notnil=true,rows=0:lng,bid=116} := sql.bind("tmp","Ttables","query",0); > T58:bat[:oid,:str]{notnil=true,rows=30:lng,bid=70} := sql.bind("sys","Ttables","query",0); > T64:bat[:oid,:bit]{notnil=true,rows=0:lng,bid=118} := sql.bind("tmp","Ttables","system",0); > T67:bat[:oid,:bit]{notnil=true,rows=30:lng,bid=72} := sql.bind("sys","Ttables","system",0); > T72:bat[:oid,:sht]{notnil=true,rows=0:lng,bid=119} := sql.bind("tmp","Ttables","commitTaction",0); > T75:bat[:oid,:sht]{notnil=true,rows=30:lng,bid=73} := sql.bind("sys","Ttables","commitTaction",0); > T8{rows=0:lng} := algebra.markT(T1,0@0); > T9{rows=0:lng} := bat.reverse(T8); > T8{rows=0:lng} := nil; > T12{rows=0:lng} := algebra.join(T9,T10); > T10:bat[:oid,:sht]{notnil=true,rows=0:lng,bid=117} := nil; > T18{rows=30:lng} := algebra.markT(T13,0@0); > T19{rows=30:lng} := bat.reverse(T18); > T18{rows=30:lng} := nil; > T21{rows=30:lng} := algebra.join(T19,T20); > T20:bat[:oid,:sht]{notnil=true,rows=30:lng,bid=71} := nil; > T22{rows=31:lng} := bat.setWriteMode(T21); > T21{rows=30:lng} := nil; > bat.append(T22,T12,true); > T12{rows=0:lng} := nil; > T26{rows=31:lng} := algebra.uselect(T22,nil:sht,2:sht,false,false); > T29{rows=31:lng} := algebra.markT(T26,0@0); > T26{rows=31:lng} := nil; > T30{rows=31:lng} := bat.reverse(T29); > T29{rows=31:lng} := nil; > T31{rows=0:lng} := algebra.join(T9,T1); > T1:bat[:oid,:int]{notnil=true,rows=0:lng,bid=113} := nil; > T32{rows=30:lng} := algebra.join(T19,T13); > T13:bat[:oid,:int]{notnil=true,rows=30:lng,bid=67} := nil; > T33{rows=31:lng} := bat.setWriteMode(T32); > T32{rows=30:lng} := nil; > bat.append(T33,T31,true); > T31{rows=0:lng} := nil; > T35{rows=31:lng} := algebra.join(T30,T33); > T36{rows=31:lng} := algebra.markT(T35,0@0); > T35{rows=31:lng} := nil; > T37{rows=31:lng} := bat.reverse(T36); > T36{rows=31:lng} := nil; > T38{rows=31:lng} := algebra.joinPath(T37,T30,T33); > T33{rows=31:lng} := nil; > T41{rows=0:lng} := algebra.join(T9,T39); > T39:bat[:oid,:str]{notnil=true,rows=0:lng,bid=114} := nil; > T43{rows=30:lng} := algebra.join(T19,T42); > T42:bat[:oid,:str]{notnil=true,rows=30:lng,bid=68} := nil; > T44{rows=31:lng} := bat.setWriteMode(T43); > T43{rows=30:lng} := nil; > bat.append(T44,T41,true); > T41{rows=0:lng} := nil; > T46{rows=31:lng} := algebra.joinPath(T37,T30,T44); > T44{rows=31:lng} := nil; > T49{rows=0:lng} := algebra.join(T9,T47); > T47:bat[:oid,:int]{notnil=true,rows=0:lng,bid=115} := nil; > T51{rows=30:lng} := algebra.join(T19,T50); > T50:bat[:oid,:int]{notnil=true,rows=30:lng,bid=69} := nil; > T52{rows=31:lng} := bat.setWriteMode(T51); > T51{rows=30:lng} := nil; > bat.append(T52,T49,true); > T49{rows=0:lng} := nil; > T54{rows=31:lng} := algebra.joinPath(T37,T30,T52); > T52{rows=31:lng} := nil; > T57{rows=0:lng} := algebra.join(T9,T55); > T55:bat[:oid,:str]{notnil=true,rows=0:lng,bid=116} := nil; > T59{rows=30:lng} := algebra.join(T19,T58); > T58:bat[:oid,:str]{notnil=true,rows=30:lng,bid=70} := nil; > T60{rows=31:lng} := bat.setWriteMode(T59); > T59{rows=30:lng} := nil; > bat.append(T60,T57,true); > T57{rows=0:lng} := nil; > T62{rows=31:lng} := algebra.joinPath(T37,T30,T60); > T60{rows=31:lng} := nil; > T63{rows=31:lng} := algebra.joinPath(T37,T30,T22); > T22{rows=31:lng} := nil; > T66{rows=0:lng} := algebra.join(T9,T64); > T64:bat[:oid,:bit]{notnil=true,rows=0:lng,bid=118} := nil; > T68{rows=30:lng} := algebra.join(T19,T67); > T67:bat[:oid,:bit]{notnil=true,rows=30:lng,bid=72} := nil; > T69{rows=31:lng} := bat.setWriteMode(T68); > T68{rows=30:lng} := nil; > bat.append(T69,T66,true); > T66{rows=0:lng} := nil; > T71{rows=31:lng} := algebra.joinPath(T37,T30,T69); > T69{rows=31:lng} := nil; > T74{rows=0:lng} := algebra.join(T9,T72); > T72:bat[:oid,:sht]{notnil=true,rows=0:lng,bid=119} := nil; > T76{rows=30:lng} := algebra.join(T19,T75); > T75:bat[:oid,:sht]{notnil=true,rows=30:lng,bid=73} := nil; > T77{rows=31:lng} := bat.setWriteMode(T76); > T76{rows=30:lng} := nil; > bat.append(T77,T74,true); > T74{rows=0:lng} := nil; > T79{rows=31:lng} := algebra.joinPath(T37,T30,T77); > T77{rows=31:lng} := nil; > T81{rows=0:lng} := algebra.project(T9,1); > T9{rows=0:lng} := nil; > T83{rows=30:lng} := algebra.project(T19,0); > T19{rows=30:lng} := nil; > T84{rows=31:lng} := bat.setWriteMode(T83); > T83{rows=30:lng} := nil; > bat.append(T84,T81,true); > T81{rows=0:lng} := nil; > T86{rows=31:lng} := algebra.joinPath(T37,T30,T84); > T37{rows=31:lng} := nil; > T30{rows=31:lng} := nil; > T84{rows=31:lng} := nil; > T87 := sql.resultSet(8,1,T38); > sql.rsColumn(T87,"sys.tables","id","int",32,0,T38); > T38{rows=31:lng} := nil; > sql.rsColumn(T87,"sys.tables","name","varchar",1024,0,T46); > T46{rows=31:lng} := nil; > sql.rsColumn(T87,"sys.tables","schemaTid","int",32,0,T54); > T54{rows=31:lng} := nil; > sql.rsColumn(T87,"sys.tables","query","varchar",2048,0,T62); > T62{rows=31:lng} := nil; > sql.rsColumn(T87,"sys.tables","type","smallint",16,0,T63); > T63{rows=31:lng} := nil; > sql.rsColumn(T87,"sys.tables","system","boolean",1,0,T71); > T71{rows=31:lng} := nil; > sql.rsColumn(T87,"sys.tables","commitTaction","smallint",16,0,T79); > T79{rows=31:lng} := nil; > sql.rsColumn(T87,"sys.tables","temporary","tinyint",8,0,T86); > T86{rows=31:lng} := nil; > sql.exportResult(T87,""); > end qry; > compiler.MALtoC("user","qry","sql01"); -- | 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

Re: [Monetdb-developers] BAT sizes
by Stefan Manegold 07 Oct '07

07 Oct '07

[felt free to cc the monetdb-developers list as more people might be interested or want to contribute] Henning, are you just "concerned" or are you having concrete problems with the bat sizes? In cany case, to give any reasonable answer we'd need to know more about the details. In particular how large is the BAT your talking about. I.e., with "b" being your BAT and "c := b.copy()", please check & report b.count(); b.info().reverse().like("batBuns").like("size").print(); b.batsize(); b.batdsksize(); c.count(); c.info().reverse().like("batBuns").like("size").print(); c.batsize(); c.batdsksize(); Stefan On Fri, Oct 05, 2007 at 01:47:01PM +0200, Henning Rode wrote: > hej stefan, > > thanks for the answer. so in conclusion, the over-allocation of memory > is quite normal, and nothing to worry about. > > i was more surprised that the copied BAT still has this considerable > over-allocation of memory, though it exactly knows how many entries it > needs to hold. > > groeten -henning -- | 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 1

Re: [Monetdb-developers] [Monetdb-bugs] JDBC: Negative Integer in Prepared Statement
by Stefan Manegold 06 Oct '07

06 Oct '07

Hi Jan, thanks for using MonetDB, and sorry for the inconvenience. We'll investigate the reported problem shortly. However, the monetdb-bugs mailing list is actually not meant to be used directly (admittedly our fault, in case we didn't communicate this clearly and/or haven't prevented direct postings, yet). The monetdb-bugs mailing list is mainly meant notify developers of newly files bug reports and their follow-up comments. Hence, could you please file your bug using the SF bug tracker at http://sourceforge.net/tracker/?atid=482468&group_id=56967&func=browse ? Thanks, Stefan On Sat, Oct 06, 2007 at 08:08:57PM +0200, Schaffner, Jan wrote: > Hi, > > When using prepared statements in Java, I am unable to pass negative > integer values to the database: > > String APPEND_JOURNAL = "INSERT INTO journal VALUES (?, ?);"; > st = con.prepareStatement(APPEND_JOURNAL); > st.setInt(1, fromAcc); > st.setInt(2, -amount); > st.executeUpdate(); > > The table "journal" has two columns: account (int) and amount (bigint). > > The insert statement executes without error, but inserts the positive > value (+amount, cf. line 4). The debugger, in contrast, says something > like "exec 3(200, -30)". Note that is has a minus in front of the > second parameter. > > Without prepared statements, however, inserting negative values works > perfactly fine. > > Thanks, > Jan -- | 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

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/tests/BugTracker/Tests noroot.SF-1452237.XQUERY.bat, XQuery_0-20, NONE, 1.1.2.1
by Sjoerd Mullender 05 Oct '07

05 Oct '07

Stefan Manegold wrote: > Update of /cvsroot/monetdb/pathfinder/tests/BugTracker/Tests > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv23002 > > Added Files: > Tag: XQuery_0-20 > noroot.SF-1452237.XQUERY.bat > Log Message: > > added Windows version --- still needs to be tested/checked! > > > --- NEW FILE: noroot.SF-1452237.XQUERY.bat --- > @XQUERY_CLIENT@ -s1 -f xml-noroot %...% -- Sjoerd Mullender

1 0

Re: [Monetdb-developers] [Monetdb-checkins] MonetDB4/tests/BugDay_2005-10-06_4.8/Tests multiple_servers.SF-914113.MIL.bat, MonetDB_4-20, NONE, 1.1.2.1
by Sjoerd Mullender 05 Oct '07

05 Oct '07

Stefan Manegold wrote: > Update of /cvsroot/monetdb/MonetDB4/tests/BugDay_2005-10-06_4.8/Tests > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv15739/MonetDB4/tests/BugDay_2005-10-06_4.8/Tests > > Added Files: > Tag: MonetDB_4-20 > multiple_servers.SF-914113.MIL.bat > Log Message: > > added Windows version --- still needs to be tested/checked! > > > --- NEW FILE: multiple_servers.SF-914113.MIL.bat --- > @call @MSERVER@ --dbname=@TSTDB@ I can tell you right away that this won't fly. Either it has to be a .in file so that the @...@ stuff gets expanded, or if they are supposed to be environment variables, they should be %...%. -- Sjoerd Mullender

1 0

Re: [Monetdb-developers] [Monetdb-pf-checkins] pathfinder/modules/pftijah nexi_generate_mil.c, XQuery_0-18, 1.33.2.3, 1.33.2.4
by Sjoerd Mullender 05 Oct '07

05 Oct '07

Djoerd Hiemstra wrote: > Update of /cvsroot/monetdb/pathfinder/modules/pftijah > In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv1427 > > Modified Files: > Tag: XQuery_0-18 > nexi_generate_mil.c > Log Message: > The ir-model="LM" option was translated to "LMs" in the algebra. You do realize that the XQuery_0-18 branch is the *old* stable branch and that we're now using XQuery_0-20? > > Index: nexi_generate_mil.c > =================================================================== > RCS file: /cvsroot/monetdb/pathfinder/modules/pftijah/nexi_generate_mil.c,v > retrieving revision 1.33.2.3 > retrieving revision 1.33.2.4 > diff -u -d -r1.33.2.3 -r1.33.2.4 > --- nexi_generate_mil.c 15 Jun 2007 08:53:00 -0000 1.33.2.3 > +++ nexi_generate_mil.c 4 Oct 2007 13:11:35 -0000 1.33.2.4 > @@ -711,7 +711,7 @@ > case MODEL_LM : > > // MILPRINTF(MILOUT, "R%d := R%d.p_containing_q_LM(terms, qenv);\n", com_num, com_nr_left); > - MILPRINTF(MILOUT, "R%d := R%d.p_containing_q_LMs%s(terms%s,qenv);\n", com_num, com_nr_left, parserCtx->ffPfx, parserCtx->flastPfx); > + MILPRINTF(MILOUT, "R%d := R%d.p_containing_q_LM%s(terms%s,qenv);\n", com_num, com_nr_left, parserCtx->ffPfx, parserCtx->flastPfx); > > break; > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Monetdb-pf-checkins mailing list > Monetdb-pf-checkins(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/monetdb-pf-checkins -- Sjoerd Mullender

5 5