Re: Autoload scripts from MonetDB/sql/scripts

ok solved it. so it turns out that if one script has an error then no script is loaded, even the ones that come numerically before the one with the error. I knew that nothing after the erroneous script may not be loaded, but was not necessarily true that anything before that will be rolled back too. I assume all autoload scripts run in a single transaction. Of course the error was not obvious from the messages hence the confusion, but once Panos told me that it works for him, I tried something else. On Tue, Sep 5, 2017 at 1:10 PM, Lefteris wrote:

Hi Stefan,

there is only one environment that I use.

Of course, once the mserver5 command is used and the scripts are executed, then if I start monetdb the effects of the scripts are there, so I know it is the same environment.

I also tried using monetdb start dbname explicitly and could not see the script effects.

BTW, I am using default branch.

Anyway, this is something to keep in mind. My guess is that I have stumbled on a weird case of the autoload functionality that might even be a bug.

On Tue, Sep 5, 2017 at 12:03 PM, Stefan Manegold wrote:

...

Maybe a "stupid" question, but I've seen this too often (and "hit" it myself):

are you sure that you have the same environment settings for both and monetdb(d) indeed call the same mserver5 as you call by hand?

Note also, that the autoload SQL scripts are only run with the first start of a server on a new virgin DB --- but that seems to be the case in your case ...

Maybe try to explicitly start the server using `monetdb start dbname` before connecting with mclient ...?

Stefan

----- On Sep 5, 2017, at 11:37 AM, Lefteris lsidir@gmail.com wrote:

...

thanx panos,

but the question here is not where the messages are, but that these scripts seems not to have any effect.

for example the 80_statistics.sql script is suppose to create a sys.statistics table, but this table is nowhere to be found, or at least I can not find it.

On Tue, Sep 5, 2017 at 11:26 AM, Panagiotis Koutsourakis wrote:

...

Hey Lefteris,

The messages should be in the merovingian.log file inside the dbfarm. As far as I know, mserver stdout and stderr, get written in that file, if you use monetdbd, although this logging is far from perfect.

Panos

Lefteris @ 2017-09-04 15:15 GMT:

...

After playing around with some udfs and such, it seems to me that the autoload feature of the scripts in directory MonetDB/sql/scripts only run if I start monetdb with the following command

mserver5 --dbpath=...

and then when I connect with mclient all these messages about loading the scripts appear at the mserver5 console.

However, if I create a dbfarm with

monetdbd create path/ monetdbd start path/

and then a database

monetdb create dbname monetdb release dbname

and connect with

mclient -lsql -d dbname

all the goodies from the script dir do not appear to be there.

Is there another trigger for this case that runs autoload?

thanx _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list

-- | Stefan.Manegold@CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ | Science Park 123 (L321) | | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) | _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list