Dear all,
I use HOST_NAME_MAX in my code. Compiling the code on a CWI machine
does not have any problem, however, compilation on Mac OS 10.5
complains that HOST_NAME_MAX is not defined. fgrep on mac 10.5 says:
$fgrep -r HOST_NAME_MAX /usr/include/*
/usr/include/limits.h:#define _POSIX_HOST_NAME_MAX 255
/usr/include/unistd.h:#define _SC_HOST_NAME_MAX 72
How (and where) can I add proper check to define HOST_NAME_MAX for
darwin 9?
Thanks!
Jennie
Hi Stefan, Riham
PF_ROX has the new indexing code, that Lefteris has tried to describe in his
recent paper. This code was only checked for correct operation from MIL in the
code generated by the pf-rox java program of Riham.
The correct operation of the new indexing code when activated automatically
from mps was not tested yet. It may well be the source of trouble. i will pick
this up once I have some time again (..).
Peter
Dear all,
I checked all (modified) files in the PF_ROX branch by hand, and all but
runtime/pathfinder.mx & runtime/pf_support.mx (this means in particular the
compiler/mil/milprint_summer.c I fixed the other day) are OK, i.e., they
contain all (intended) changes applied in the PF_ROX branch as well as all
chnages that were made on the development trunk since the creation of the
PF_ROX branch (and hence properly propagated).
For runtime/pathfinder.mx & runtime/pf_support.mx, I am not yet sure,
whether everything is OK. There have been numerous "interleaved" (and partly
"redundant" or "conflicting") changes both genuine on the PF_ROX branch and
propagated from the development trunk, and the (very tedious) analysis
requires more time than I could spent today.
More to come "soon", I hope ...
Unfortunately, while only 50 (100) tests fail in the new stable branch (and
in the development trunk), more than 500 tests seem to fail in the PF_ROX
branch --- also this requires "some" more ananlysis ...
Stefan
Propagation has been prevented.
Stefan
On Tue, May 27, 2008 at 04:48:00PM +0000, Romulo Goncalves wrote:
> Update of /cvsroot/monetdb/sql/src/test/Tests
> In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv5851
>
> Modified Files:
> Tag: SQL_2-24
> All
> Log Message:
> Deactivated
> crashme
> 50ways
>
> These are tests to be tested on the current branch and not in the stable.
> In the previous release we had the same procedure...
>
> Note: Do not propagated this change to the current one...
>
>
> U All
> Index: All
> ===================================================================
> RCS file: /cvsroot/monetdb/sql/src/test/Tests/All,v
> retrieving revision 1.51
> retrieving revision 1.51.2.1
> diff -u -d -r1.51 -r1.51.2.1
> --- All 6 Mar 2008 08:33:16 -0000 1.51
> +++ All 27 May 2008 16:47:58 -0000 1.51.2.1
> @@ -88,8 +88,8 @@
> setoptimizer
> load_dec_as_int
> string
> -NOT_WIN32?crashme
> -NOT_WIN32?50ways
> +#NOT_WIN32?crashme
> +#NOT_WIN32?50ways
> load_with_offset
> copy_into
> antiselect
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Monetdb-sql-checkins mailing list
> Monetdb-sql-checkins(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monetdb-sql-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 |
Hi,
Maybe I should move this to the users part, if so, please inform me.
What is currently the best practice of connecting to MonetDB5/SQL? Is
there much overhead in the connection phase (thus: cache the connection)
or can a developer just reconnect each time the database connection is
required without much overhead?
The target platform is extremely demanding in requests and memory, so I
would like to design it good from the start.
Stefan
Dear fellow MonetDB developers,
this is to keep you up-to-date about the short-term release plans for the
MonetDB product family as they have recently been discussed here at CWI in
A'dam.
Please read until the end.
Thank you very much in advance for your patience ans cooperation!
Triggered by (1) the major progress in extending the functionality of the
new "Algebra back-end" based version of Pathfinder (MonetDB/XQuery) to
(almost) meet the functionality as provided by the (til date) default
"milprint_summer back-end" based version (see details below), and (2) the
desire of at least one distinct client to use the new "Algebra back-end"
based version of Pathfinder (MonetDB/XQuery), we plan to have a new release
of Pathfinder (MonetDB/XQuery), soon.
Unfortunately, the functionality of the new "Algebra back-end" based version
of Pathfinder (MonetDB/XQuery) is not yet identical with that of the (til
date) default "milprint_summer back-end" based version. First of all,
extensions beyond the XQuery and XQuery Updates standards, such as XRpc,
StandOff, and pre-compiled XQuery modules ("MIL modules") are not supported,
as well as recursive user-defined functions are not supported, yet.
(The not yet working id/idref functionality is currently being implemented.)
Moreover, the XQuery Update functionality is not yet complete/correct, as it
cannot yet handle inserts of node who's type is not statically known at query
compile time.
In particular the latter shortcoming currently keeps us from our original
plans of making the new "Algebra back-end" the default in the upcoming
release. Hence, most probably, the upcoming release will still come with the
"milprint_summer back-end" set as default. However, as already in the latest
release, runtime options allow users to easily enable the new "Algebra
back-end".
Some (internal) API changes on the development trunk since the last release
(mainly the signatures of GDK functions BAT_select(), BATmmap() &
BATmadvice()), prohibit a new "feature release" of pathfinder, only, as this
is incompatible with currently available releases of MonetDB4 (Server) and
MonetDB (Common).
Hence, also this upcoming release will be a "complete" one, i.e., all
MonetDB related packages (MonetDB Common, Clients, MonetDB4 Server, MonetDB5
Server, MonetDB/SQL, MonetDB/Geom & MonetDB/XQuery will (have to be)
released.
Given this, our plan is as follows:
Within the next week, we will fork new "Stable" branches of the current
development trunks.
Please let us know at your earliest convenience, in case you have new feature
developments "in the pipe", that should go into the new release.
In case you have just started new "cutting edge" developments that are still
far from mature to be released soon, please refrain from checking them in
until the new release branches have been created.
Once the new release branches are created, we plan to spend about one month
on thoroughly testing and stabilizing the new release and its packaging.
Any help from all of you is highly appreciated!
In particular, we count on the support for all "first users" of the new
Pathfinder (MonetDB/XQuery) "Algebra back-end' (even if it will not be the
default choice).
The envisioned release date is "End of June".
Please let us know, in case you have any questions, comments, suggestions,
etc.
Yours Sincerely,
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 |
Hi,
I would like to know if your SQL engine is independant enough from
MonetDB in order to let me reasonably write my own SQL engine storage
backend?
(Not I dislike MonetDB, just that for the moment I use a custom disk
storage and would try to put a SQL engine on top of it)
Best regards,
Sylvain B.
--
use single GPL licensed software, use Linux and secure your digital freedom!