-
Closing.
Gijs, now you should be able to do that yourself. You could have asked...
2010-01-05 15:44:46 UTC in MonetDB
-
Mclient cannot read your mind. You tell it what encoding to use. The default is to use the locale (LC_CTYPE which defaults to LANG but in your case is different), and if that isn't the correct encoding you can tell it what the correct encoding is with the -E option. There is no bug here.
2010-01-04 21:37:20 UTC in MonetDB
-
I agree that the error code of mclient is not right. I just fixed that in the code.
mclient uses the LC_CTYPE value to determine the encoding of the terminal. In your case that is "C", so that means that you (implicitly) told mclient that it can only write ASCII data. Converting the e with diaeresis to ASCII is not possible, so mclient bails.
If your terminal can do more than ASCII, you...
2010-01-04 19:52:54 UTC in MonetDB
-
What is your locale? Give the command
locale
in a shell and post the result.
mclient uses your locale to determine how to translate the UTF-8 characters it gets from the server to whatever your terminal window uses. If your locale is e.g. C, then there is no way to translate the "e with diaeresis" in the table, so mclient complains about that (the write error you reported). I admit, the...
2010-01-04 18:58:04 UTC in MonetDB
-
I must say, I found the theory that the BSS wasn't cleared very strange. The C language specification guarantees that all static and global (i.e. anything not on the stack) variables are initialized to a zero bit pattern (if not initialized explicitly).
2010-01-04 08:56:17 UTC in MonetDB
-
mclient sends quite large buffers to the server, and the server then find an error with one of the queries in that buffer and tells mclient that it found an error. There is a shortcoming in the protocol that the server doesn't tell mclient which query in the buffer caused the error, so mclient doesn't know that. All mclient can do is tell you that somewhere in the buffer it sent there was an...
2009-12-23 13:20:53 UTC in MonetDB
-
Fixed in CVS.
2009-12-15 08:58:51 UTC in MonetDB
-
This means there is no server running.
2009-12-14 11:48:07 UTC in MonetDB
-
Probably you have an MonetDB5/SQL server running when you tried starting the MonetDB4/XQuery server. Those servers cannot both run at the same time (in the default Windows configuration). So, stop the SQL server, then start the XQuery server, then start the XQuery client.
2009-12-14 08:49:24 UTC in MonetDB
-
We made an error when packaging the Windows package, we forgot to include some new files in the installer.
Since the Nov2009-SP1 release is about to be created and tested, I can provide the (first?) release candidate for you to test. See .
2009-12-10 12:25:47 UTC in MonetDB
