mapi.connect / mapi_connect (Second Try)
I wrote an email a few days ago to the effect that I could not get the mapi.connect() MAL statement to work due to the server side complaining that I had not specified the database to use. This morning I ran one of the sample programs included with MonetDB, clients/examples,C/sample0.c (sample0). It seems very similar as it issues a mapi_connect() with the database field set to NULL. It fails in the same way, i.e., MAPI = monetdb@localhost:50000 ACTION= mapi_start_talking ERROR = !monetdbd: please specify a database Should mapi_connect() work with the database field set to NULL? (If so, then the mapi.connect() MAL statement should work, I think.) Is there a bug in the server that insists on the database being specified? If there is a bug, does anyone have a fix for this? It would be greatly appreciated. Thanks, Steve Morgan
On 11-03-2013 08:30:01 -0700, Stephen P. Morgan wrote:
I wrote an email a few days ago to the effect that I could not get the mapi.connect() MAL statement to work due to the server side complaining that I had not specified the database to use.
This morning I ran one of the sample programs included with MonetDB, clients/examples,C/sample0.c (sample0). It seems very similar as it issues a mapi_connect() with the database field set to NULL. It fails in the same way, i.e.,
MAPI = monetdb@localhost:50000 ACTION= mapi_start_talking ERROR = !monetdbd: please specify a database
Should mapi_connect() work with the database field set to NULL? (If so, then the mapi.connect() MAL statement should work, I think.) Is there a bug in the server that insists on the database being specified? If there is a bug, does anyone have a fix for this? It would be greatly appreciated.
No, you should pass the database name, otherwise the server can't know which one you'd like to connect to. -- Fabian Groffen fabian@monetdb.org column-store pioneer http://www.monetdb.org/Home
Then the sample0 program is incorrect, as it passes NULL in the database field.
________________________________
From: Fabian Groffen
I wrote an email a few days ago to the effect that I could not get the mapi.connect() MAL statement to work due to the server side complaining that I had not specified the database to use.
This morning I ran one of the sample programs included with MonetDB, clients/examples,C/sample0.c (sample0). It seems very similar as it issues a mapi_connect() with the database field set to NULL. It fails in the same way, i.e.,
MAPI = monetdb@localhost:50000 ACTION= mapi_start_talking ERROR = !monetdbd: please specify a database
Should mapi_connect() work with the database field set to NULL? (If so, then the mapi.connect() MAL statement should work, I think.) Is there a bug in the server that insists on the database being specified? If there is a bug, does anyone have a fix for this? It would be greatly appreciated.
No, you should pass the database name, otherwise the server can't know which one you'd like to connect to. -- Fabian Groffen fabian@monetdb.org column-store pioneer http://www.monetdb.org/Home _______________________________________________ developers-list mailing list developers-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/developers-list
In fact, then all of the sample programs, sample0.c--sample4.c and
smack00.c--smack01,c pass NULL for the database field.
________________________________
From: Stephen P. Morgan
I wrote an email a few days ago to the effect that I could not get the mapi.connect() MAL statement to work due to the server side complaining that I had not specified the database to use.
This morning I ran one of the sample programs included with MonetDB, clients/examples,C/sample0.c (sample0). It seems very similar as it issues a mapi_connect() with the database field set to NULL. It fails in the same way, i.e.,
MAPI = monetdb@localhost:50000 ACTION= mapi_start_talking ERROR = !monetdbd: please specify a database
Should mapi_connect() work with the database field set to NULL? (If so, then the mapi.connect() MAL statement should work, I think.) Is there a bug in the server that insists on the database being specified? If there is a bug, does anyone have a fix for this? It would be greatly appreciated.
No, you should pass the database name, otherwise the server can't know which one you'd like to connect to. -- Fabian Groffen fabian@monetdb.org column-store pioneer http://www.monetdb.org/Home _______________________________________________ developers-list mailing list developers-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/developers-list
On 2013-03-11 16:34, Fabian Groffen wrote:
On 11-03-2013 08:30:01 -0700, Stephen P. Morgan wrote:
I wrote an email a few days ago to the effect that I could not get the mapi.connect() MAL statement to work due to the server side complaining that I had not specified the database to use.
This morning I ran one of the sample programs included with MonetDB, clients/examples,C/sample0.c (sample0). It seems very similar as it issues a mapi_connect() with the database field set to NULL. It fails in the same way, i.e.,
MAPI = monetdb@localhost:50000 ACTION= mapi_start_talking ERROR = !monetdbd: please specify a database
Should mapi_connect() work with the database field set to NULL? (If so, then the mapi.connect() MAL statement should work, I think.) Is there a bug in the server that insists on the database being specified? If there is a bug, does anyone have a fix for this? It would be greatly appreciated.
No, you should pass the database name, otherwise the server can't know which one you'd like to connect to.
It's a bit more subtle than this. If you use merovingian (a.k.a. monetdbd), you need to specify the database name. If you're using mserver5 directly, you don't. The sample* programs don't use merovingian. -- Sjoerd Mullender
How can I get programs to use mserver5 instead of merovingian (monetdbd)? I'm
new to MonetDB.
________________________________
From: Sjoerd Mullender
On 11-03-2013 08:30:01 -0700, Stephen P. Morgan wrote:
I wrote an email a few days ago to the effect that I could not get the mapi.connect() MAL statement to work due to the server side complaining that I had not specified the database to use.
This morning I ran one of the sample programs included with MonetDB, clients/examples,C/sample0.c (sample0). It seems very similar as it issues a mapi_connect() with the database field set to NULL. It fails in the same way, i.e.,
MAPI = monetdb@localhost:50000 ACTION= mapi_start_talking ERROR = !monetdbd: please specify a database
Should mapi_connect() work with the database field set to NULL? (If so, then the mapi.connect() MAL statement should work, I think.) Is there a bug in the server that insists on the database being specified? If there is a bug, does anyone have a fix for this? It would be greatly appreciated.
No, you should pass the database name, otherwise the server can't know which one you'd like to connect to.
It's a bit more subtle than this. If you use merovingian (a.k.a. monetdbd), you need to specify the database name. If you're using mserver5 directly, you don't. The sample* programs don't use merovingian. -- Sjoerd Mullender
On 11-03-2013 09:59:28 -0700, Stephen P. Morgan wrote:
How can I get programs to use mserver5 instead of merovingian (monetdbd)? I'm new to MonetDB.
What I was aiming at is to avoid you doing that, unless you're on Windows, of course. Perhaps try the getting started quide. -- Fabian Groffen fabian@monetdb.org column-store pioneer http://www.monetdb.org/Home
On 2013-03-11 23:30, Fabian Groffen wrote:
On 11-03-2013 09:59:28 -0700, Stephen P. Morgan wrote:
How can I get programs to use mserver5 instead of merovingian (monetdbd)? I'm new to MonetDB.
What I was aiming at is to avoid you doing that, unless you're on Windows, of course. Perhaps try the getting started quide.
I'm with Fabian on this one. Use merovingian. Using mserver5 directly is only recommended for developers. -- Sjoerd Mullender
participants (3)
-
Fabian Groffen -
Sjoerd Mullender -
Stephen P. Morgan