Any chance the Python client could be modified to
return strings in Unicode instead of UTF-8?
Seems like a better fit for Python; for example,
that's how Python's sqlite3 module behaves.
An alternative approach is to expose a set_encoding
method on the connection that let's you specify the
encoding of all text fields returned.
If backward compatibility is an issue, the latter idea
seems better even though it adds a knob.
Any comments?
(Is the maintainer of the Python adapter active even
on this list? I didn't see many Python-specific posts
in the archives.)
Thanks,
m
Hello MonetDB developers,
In my quest to develop an object oriented interface to monetdb/xquery
on ruby using datamapper, I've stumbled upon the following problem. It
is at this moment impossible to add a document to monetdb that does
not have a source outside monetdb. The only function to add documents
to monetdb seems to be pf:add-doc, which takes an url parameter with a
location of an xml document it should import. To fully abstract the
database from the ruby application, it would be nice if the developers
could add a new (empty) document to the database.
Would it be a nice idea to have the following function:
pf:new-doc("document_name.xml"[,
"collection_name.xml"[,"<some><initial>content</initial></some>"]])
It would make users of my api a little happier, and perhaps
MonetDB/XQuery as a whole, a bit more normal ;)
Kind regards,
Tinco Andringa
Dear MonetDB developers,
on concurrently running writing transactions, I am getting a rather
narrowly descriptive error message: "!SQLException:sql.trans:COMMIT:
failed".
My first attempts to deal with this issue suggest that it happens
exactly in those cases where the concurrent writes create some sort of
conflict.
I am aware that MonetDB does not focus on concurrency, and of the
suggestion to serialize multiple writers. However, I'd like to
know what the current status of concurrency is. To what extent are SQL
primitives implemented which allow to let the server take care of
serializing writes, for example through explicit table locking or
transaction isolation?
Best regards,
Isidor Zeuner
Fabian wrote:
> Update of /cvsroot/monetdb/MonetDB5/src/optimizer
> In directory sfp-cvsdas-1.v30.ch3.sourceforge.com:/tmp/cvs-serv10474
>
> Modified Files:
> opt_mapreduce.mx
> Log Message:
> One of the optimisers 'inline,remap,evaluate,costModel,coercions,emptySet,aliases' replaces a nil statement in such a way that it ends up as argument 'nil' witout type, causing execution to fail. Push barrier up, such that we don't get undefined var errors because the reduce phase was performed in the dataflow block too.
You can freeze the type of variables using setVarUDFtype.
As a line of defense, at the end of an optimizer all non-UDFtypes are thrown away and a fresh
type resolve step is taken.
the tokenizer has been removed from the Makefile.ag of the stable
branch, and this #include can be deleted all the way. I have said many
times that none of this code is ready for stable branches and yes they
should have never been propagate to the stable. We haven't announced
any MonetDB/RDF module official so it should not be used by any user.
For me the #if 0 is not a problem
On Mon, Feb 22, 2010 at 4:46 PM, Fabian Groffen <Fabian.Groffen(a)cwi.nl> wrote:
> On 22-02-2010 15:43:44 +0000, Lefteris Sidirourgos wrote:
>> Update of /cvsroot/monetdb/MonetDB5/src/modules/mal/rdf
>> In directory sfp-cvsdas-1.v30.ch3.sourceforge.com:/tmp/cvs-serv32552/src/modules/mal/rdf
>>
>> Modified Files:
>> Tag: Feb2010
>> rdf_shredder.mx
>> Log Message:
>> disable the tokenizer.mx from m5
>
> Dunno if this was/is discussed, but isn't it a much cleaner solution to
> just remove it from the code base in this branch, and keep it as is in
> the HEAD (e.g. request to prevent propagation?). The 'if 0's and
> commented out code look a bit messy.
>
>
>> Index: rdf_shredder.mx
>> ===================================================================
>> RCS file: /cvsroot/monetdb/MonetDB5/src/modules/mal/rdf/rdf_shredder.mx,v
>> retrieving revision 1.13
>> retrieving revision 1.13.2.1
>> diff -u -d -r1.13 -r1.13.2.1
>> --- rdf_shredder.mx 8 Jan 2010 12:08:58 -0000 1.13
>> +++ rdf_shredder.mx 22 Feb 2010 15:43:41 -0000 1.13.2.1
>> @@ -27,7 +27,9 @@
>> #include "url.h"
>> #include "rdf.h"
>> #include "raptor.h"
>> +#if 0
>> #include "../tokenizer.h"
>> +#endif
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Monetdb-checkins mailing list
> Monetdb-checkins(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monetdb-checkins
>
On Sun, Feb 21, 2010 at 08:41:08AM +0000, Martin Kersten wrote:
> Update of /cvsroot/monetdb/MonetDB5/src/modules/kernel
> In directory sfp-cvsdas-1.v30.ch3.sourceforge.com:/tmp/cvs-serv5630
>
> Modified Files:
> Tag: Feb2010
> calc.mx
> Log Message:
> The semantics assumed overflow to produce nil-values, not an exception.
Is this in line with SQL semantic (requirements)?
AFAIK, SQL standard requires to report under-/overflows during casts as
execption/errors.
Moreover, our SQL compiler/front-end cannot (easily) destinguish between
NULL (NIL) values that have been in the input and NULL (NIL) values that are
added to the result of a cast to indicate under-/overflows.
This might have been the reason why this execption was added by Niels ...
Just my €0.02 (or less)
Stefan
>
> Index: calc.mx
> ===================================================================
> RCS file: /cvsroot/monetdb/MonetDB5/src/modules/kernel/calc.mx,v
> retrieving revision 1.96
> retrieving revision 1.96.2.1
> diff -u -d -r1.96 -r1.96.2.1
> --- calc.mx 10 Jan 2010 15:30:59 -0000 1.96
> +++ calc.mx 21 Feb 2010 08:41:02 -0000 1.96.2.1
> @@ -1273,8 +1273,10 @@
> {
> if (*a == @2_nil @3) {
> *res= @1_nil;
> +/* obey semantics above, don't check for information loss
> if (*a != @2_nil)
> throw(MAL, "calc.@1", ARGUMENT_TOO_LARGE);
> +*/
> } else {
> *res= @4;
> }
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> 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-4199 |