Hoi Stefan,
Dit zou toch niet nodig hoeven zijn. Dit wordt al geregeld via de conditional in de makefile van /sql/backends/monet5/, of vergis ik mij?
De andere checkin zal ik even onthouden voor een volgende keer.
Arjen
----- Original Message -----
> From: "Stefan Manegold" <commits(a)monetdb.org>
> To: checkin-list(a)monetdb.org
> Sent: Tuesday, October 29, 2013 9:44:26 AM
> Subject: MonetDB: default - (try to) run GSL tests only if we do have GSL...
>
> Changeset: bb53a64a83fe for MonetDB
> URL: http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bb53a64a83fe
> Modified Files:
> sql/backends/monet5/gsl/Tests/All
> Branch: default
> Log Message:
>
> (try to) run GSL tests only if we do have GSL support
>
>
> diffs (8 lines):
>
> diff --git a/sql/backends/monet5/gsl/Tests/All
> b/sql/backends/monet5/gsl/Tests/All
> --- a/sql/backends/monet5/gsl/Tests/All
> +++ b/sql/backends/monet5/gsl/Tests/All
> @@ -1,2 +1,2 @@
> -gsl00
> -gsl01
> +HAVE_GSL?gsl00
> +HAVE_GSL?gsl01
> _______________________________________________
> checkin-list mailing list
> checkin-list(a)monetdb.org
> https://www.monetdb.org/mailman/listinfo/checkin-list
>
Hi,
I am looking for a way for a MAL user function to return more than one BAT without success.
Could you give me some help?
I tried the following way:
user.test(X_1:bat[:oid,:oid], X_2:bat[:oid,:int]):void;
sql.init();
X_0 := sql.mvc();
X_1 := sql.bind(...);
X_2 := sql.bind(...);
end test;
X1:bat[:oid,:oid] := bat.new(:oid,:oid);
X2:bat[:oid,:int] := bat.new(:oid,:int);
X_1:str := remote.put(url, X1);
X_2:str := remote.put(url, X2);
X_3:str := remote.exec(url, "user", "test", X_1, X_2);
X3:bat[:oid,:oid] := remote.get(url, X_1);
X4:bat[:oid,:int] := remote.get(url, X_2);
io.print(X3);
io.print(X4);
I am using python-monetdb 11.16.0.7. I created my database farm and
database according to instructions given below (source:
http://www.monetdb.org/Documentation/monetdbd)
% monetdbd start /home/my-dbfarm
% monetdb create my-first-db
Then I tried to connect to the database using the below mentioned command
in python(https://pypi.python.org/pypi/python-monetdb/). Upon doing so I am
getting the below mentioned error:
>import monetdb.sql
>connection=monetdb.sql.connect(username="monetdb",password="monetdb",hostname="localhost",database="my-first-db");
File
"/usr/local/lib/python2.7/dist-packages/monetdb/sql/__init__.py", line 28,
in connect
return Connection(*args, **kwargs)
File
"/usr/local/lib/python2.7/dist-packages/monetdb/sql/connections.py", line
58, in __init__
unix_socket=unix_socket)
File "/usr/local/lib/python2.7/dist-packages/monetdb/mapi.py",
line 93, in connect
self.socket.connect((hostname, port))
File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 111] Connection refused
Can someone please help me with this?
Also my my-first-db resides inside my db-farm? I am not getting as to what
should I do?
The MonetDB team at CWI/MonetDB BV is pleased to announce the
Feb2013-SP5 bugfix release of the MonetDB suite of programs.
More information about MonetDB can be found on our website at
<http://www.monetdb.org/>.
For details on this release, please see the release notes at
<http://www.monetdb.org/Downloads/ReleaseNotes>.
As usual, the download location is <http://dev.monetdb.org/downloads/>.
Feb 2013-SP5 bugfix release
Client Package
* ODBC: Implemented retrieving variable-length data in parts with
SQLGetData. See bug 3381.
MonetDB Common
* Removed the heap cache. Since the fix for bug 3323 which made that
the cache was actually getting used, bug 3376 made clear that it
didn't work very well. In addition, on Linux at least, the heap
cache slows things down.
Java Module
* Rearranged order of returned columns of certain metadata functions
to comply with the JDBC documentation. See bug 3356.
Bug Fixes
* 3323: Heapcache bugs/performance issues
* 3331: SAMPLE will return same result every time.
* 3356: DatabaseMetaData.getColumns() doesn't work correctly when
using index-based getters
* 3367: Fully qualified order by column gives "relational query
without result"
* 3368: BAT sortedness info ignored on ORDER BY and TOPN
* 3370: SQL environment settings are updated even when the set
statement fails
* 3373: Setting table to read-only (Bug 3362) fails on big-endian
* 3375: LIKE join: BATfetchjoin does not hit always
* 3376: COPY INTO fails with HEAPextend: failed to extend:
MT_mremap() failed
* 3377: Query interfering with next query in same transaction, after
SP4
* 3380: Python DBAPI driver throws exception when fetching EXPLAIN
results
* 3381: Windows ODBC driver hangs or crashes on simple queries
I created monetdb database using the python library
https://pypi.python.org/pypi/python-monetdb/11.16.0.7 on my ubuntu 12.04
lts server. Now I want to transfer this database to another ubuntu 12.04
lts server. However, I am unable to understand as to where(directory name)
does monetdb create its database (within ubuntu 12.04) and what is the
procedure which I must follow to transfer this database to another machine
(so that i may query the database on another machine)?
Hi Pete and List,
On 10/09/2013 09:50 AM, Pete Hollobon wrote:
> Thank you for this, we'll give it a try.
Great!
> Can this version be used with an existing dbfarm, or is a dump / load
> necessary?
This should work fine with other Feb2013 dbfarms.
best,
Hannes
Hi monetDB people,
The sqlalchemy dialect for monetdb is in quite good shape now, so I made
a 0.1 release. It is also available throught Pypi. anybody who wants to
give it a test and has some feedback, check it out:
https://github.com/gijzelaerr/sqlalchemy-monetdb
To add support for the upcomming 0.9 release I had to modify the MonetDB
Python API a bit, so it support subtypes of python build-in types. I've
added some unittests so the test output will change. Can one of you
update the test output, I don't have a the monetdb testing output update
script working on this machine.
greetings,
--
Gijs Molenaar
http://www.astro.uva.nl/people/gijs-molenaar/
Hi MonetDB people,
I encountered this TODO message while running a query:
sql>SELECT objects.name
more> FROM sys.keys, sys.objects, sys.tables, sys.schemas
more> WHERE sys.keys.id = objects.id
more> AND keys.table_id = tables.id
more> AND tables.schema_id = schemas.id
more> AND keys.type = 0
more> AND tables.id = 11323;
TODO: column names of level >= 3
--
Gijs Molenaar
http://www.astro.uva.nl/people/gijs-molenaar/