timestamp(0).print;
[ 1970-01-01 01:00:00.000 ]
--------^
Should this not be 1970-01-01 00:00:00.000?
Or has this todo with the Daylight Savings time?
--
Arjan Scherpenisse
Centrum voor Wiskunde en Informatica,
Amsterdam, the Netherlands
Dear Open Source developer
I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.
With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.
With many thanks for your participation,
Benno Luthiger
PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fasd(a)webboard.ethz.ch for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.
_______________________________________________________________________
Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich
Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________
Dear fellow developers,
after recent changes, the latest SQL (intendedly) does not compile with the
stable MonetDB-4.3.16, anymore.
Moreover, we plan to have some "major" changes both on MonetDB and on SQL
during the summer heading for the first "official" release MonetDB 4.4 in
autumn.
Hence, Niels and I had the idea to make a "snapshot" or "intermediate
stable" (pre-)release just before we start with major changes.
The proposal is to start new release candidate branches, both for MonetDB
and SQL (named MonetDB_4-3-18 and SQL_2-0-18, respectively) sometime this
week (i.e., before end of May), getting them, stable as soon as possible,
and aim for a release date about mid June.
The current MonetDB code base seems to be doing quite well, hence I do not
expect too much work, here, unless we plan to have some more new features
(Peter: xtables, aggregates, ...?; Stefan: merged-union?) in the code.
I guess, the same holds for SQL, but I'm not that sure, there.
Are there any other features, that should be included in this "intermediate
release"?
A new "stable" also means, that all add-ons that are currently tested with
4-3-16 need to be ported to 4-3-18 (i.e., XML, PathFinder (HEAD), pruning,
misq, gis, acoi) --- which probably requires a careful check, that
monetdb_config.h is included in the local *_config.h's, and that the latter
one is the FIRST include file in EACH .c file...
Any other comments, complaints, suggestions, ...?
Open issues (all, mine, I'm afraid |-() are:
- testing on AIX (sara, "batch mode"),
- testing on medusa (in Tilburg),
- testing on native WindowsXP + VS .NET (on Sjoerd's machine)
- clean-up / re-implementation of TestTools
Stefan
ps: we could of course also postpone this action until after the ICDE
deadline on July 2nd and condense it to at most one week ...
--
| 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 |
I have made a RFE for this, including the patch (-u).
https://sourceforge.net/tracker/index.php?func=detail&aid=951859&group_id=5…
Sjoerd Mullender wrote:
> Arjan Scherpenisse wrote:
>
> Please use a context diff for patches (-c or -u option).
> I think this should go in the SourceForge RFE (Request For Enhancement)
> tracker (with the patch as attachment).
> It should be configurable (both whether, and where), and probably off by
> default.
> On Windows it is by no means certain that C: exists nor that C:\ is
> writable by Joe Random Luser.
> What about errors?
>
> Having said all of this, I think a patch like this has potential and
> could be included.
>
>> regards,
>>
>>
>> ------------------------------------------------------------------------
>>
>> Index: MapiClient.mx
>> ===================================================================
>> RCS file: /cvsroot/monetdb/MonetDB/src/mapi/clients/C/MapiClient.mx,v
>> retrieving revision 1.56
>> diff -r1.56 MapiClient.mx
>> 854a855,857
>>
>>> #ifdef HAVE_LIBREADLINE
>>> char history_file[100];
>>> #endif
>>
>>
>> 1000a1004,1012
>>
>>> #ifdef HAVE_LIBREADLINE
>>> #ifndef NATIVE_WIN32
>>> snprintf(history_file, 100, "%s/.mapiclient_history",
>>> getenv("HOME"));
>>> #else
>>> snprintf(history_file, 100, "C:\\_mapiclient_history");
>>> #endif
>>> read_history(history_file);
>>> #endif
>>>
>>
>> 1016a1029,1033
>>
>>> #ifdef HAVE_LIBREADLINE
>>> write_history(history_file);
>>> #endif
>>>
>
>
--
Arjan Scherpenisse
Centrum voor Wiskunde en Informatica,
Amsterdam, the Netherlands
> I have written a small patch so mapiclient remembers the query history
> > between sessions. Maybe this could be included in CVS.
well, if it is tested, "save" (see comments below), and documented (see
`Mx -H1 -w MapiClient.mx ; links MapiClient.html` or
`Mx -H1 -t MapiClient.mx ; latex MapiClient.tex ; xdvi MapiClient.dvi`),
go ahead ;-)
Stefan
> regards,
> --
> Arjan Scherpenisse
>
> Centrum voor Wiskunde en Informatica,
> Amsterdam, the Netherlands
>
> Index: MapiClient.mx
> ===================================================================
> RCS file: /cvsroot/monetdb/MonetDB/src/mapi/clients/C/MapiClient.mx,v
> retrieving revision 1.56
> diff -r1.56 MapiClient.mx
> 854a855,857
> > #ifdef HAVE_LIBREADLINE
> > char history_file[100];
^^^
what about using PATHLENGTH ?
> > #endif
> 1000a1004,1012
> > #ifdef HAVE_LIBREADLINE
> > #ifndef NATIVE_WIN32
> > snprintf(history_file, 100, "%s/.mapiclient_history", getenv("HOME"));
^^^^
what happens if $HOME is not set?
> > #else
> > snprintf(history_file, 100, "C:\\_mapiclient_history");
> > #endif
> > read_history(history_file);
what happens, if history_file does not exist or is not readable?
> > #endif
> >
> 1016a1029,1033
> >
> > #ifdef HAVE_LIBREADLINE
> > write_history(history_file);
what happens if $HOME or history_file is not writeable?
> > #endif
> >
>
--
| 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 |
I have written a small patch so mapiclient remembers the query history
between sessions. Maybe this could be included in CVS.
regards,
--
Arjan Scherpenisse
Centrum voor Wiskunde en Informatica,
Amsterdam, the Netherlands
Index: MapiClient.mx
===================================================================
RCS file: /cvsroot/monetdb/MonetDB/src/mapi/clients/C/MapiClient.mx,v
retrieving revision 1.56
diff -r1.56 MapiClient.mx
854a855,857
> #ifdef HAVE_LIBREADLINE
> char history_file[100];
> #endif
1000a1004,1012
> #ifdef HAVE_LIBREADLINE
> #ifndef NATIVE_WIN32
> snprintf(history_file, 100, "%s/.mapiclient_history", getenv("HOME"));
> #else
> snprintf(history_file, 100, "C:\\_mapiclient_history");
> #endif
> read_history(history_file);
> #endif
>
1016a1029,1033
>
> #ifdef HAVE_LIBREADLINE
> write_history(history_file);
> #endif
>
Because I forgot to checkin a file yesterday (since corrected), testing
failed on all platforms except Native Windows.
--
Sjoerd Mullender <sjoerd(a)acm.org>
Hi,
Maybe it would be a good idea to include some information about the
build date on startup of Mserver, just like other programs do that
(Linux uname -a, Python, etc). That way you quickly can see if you have
the latest version...
druif:~/> Mserver
# Monet Database Server V4.3.17 (Apr 27 2004, 14:27:43) <-----
# Copyright (c) 1993-2004, CWI. All rights reserved.
# Compiled for i686-pc-linux-gnu/32bit; dynamically linked.
# Visit http://monetdb.cwi.nl for further information.
monet>
regards
--
Arjan Scherpenisse
Centrum voor Wiskunde en Informatica,
Amsterdam, the Netherlands
Hello,
I am writing a MIL module which exports some functions for computation
of different forms of string similarities. I would love to add this
module to monet CVS (so I won't have to patch any Makefiles and copy
source files whenever I do a new checkout), but I'm hesitating because I
am not sure what the policy is for adding functions, library bindings,
etc to Monet. Should it go in a separate CVS repository, or should it
not be included at all? Could someone elaborate on this?
regards
--
Arjan Scherpenisse
Centrum voor Wiskunde en Informatica,
Amsterdam, the Netherlands