- developers-list - monetdb.org

Re: read BLOB column on tail heap and loop over rows
by Anton Kravchenko 13 Nov '17

13 Nov '17

Ok, here is a workaround [though I suspect that performance is going to degrade (with respect to CHAR column for example[1]) because BUNtail is being called for each row...] sql_column *col = mvc_bind_column(m, tbl, colname[icol]); BAT *b = table_funcs.full_column(m->session->tr, col); //read the entire column into continuous memory on the tail heap of the BAT b BATiter *iterators = NULL; blob *blob_record; int ib; iterators = GDKzalloc(sizeof(BATiter)); iterators[0] = bat_iterator(b); // blob column iterator for (irow=0; irow < nrow; irow++) { blob_record = (blob*) BUNtail(iterators[0], irow); for (ib=0; ib < blob_record->nitems; ib++) { printf("blob data = %c, %02x\n", blob_record->data[ib], blob_record->data[ib]); } } p.s. [1] //For CHAR column it would look like this: sql_column *col = mvc_bind_column(m, tbl, colname[icol]); BAT *b = table_funcs.full_column(m->session->tr, col); //read the entire column into continuous memory on the tail heap of the BAT b char *tvbase, *cptr; unsigned char *readucrows; tvbase = (char *) b->T.vheap->base + GDK_VAROFFSET; readucrows = (unsigned char *) b->T.heap.base; for (irow=0; irow < nrow; irow++) { cptr = tvbase + *readucrows++; } Anton On Fri, Nov 10, 2017 at 4:13 PM, Anton Kravchenko < kravchenko.anton86(a)gmail.com> wrote: > I wonder how one would read BLOB column and loop over its rows? > > BAT *b = table_funcs.full_column(m->session->tr, blob_col_name); > //blob *readblobrows = (blob*) b->T.heap.base; > //unsigned char *readblobrows = (unsigned char*) b->T.heap.base; > > p.s. > For INT column it would be go like this: > int * readintrows = (int *) b->T.heap.base; > for (irow=0; irow < nrow; irow++) { > intvalue = *readintrows++; > } > > Thanks, > Anton >

1 0

Re: MonetDB: Jul2017 - Properly respect DEFAULT values in the Python...
by Stefan Manegold 13 Nov '17

13 Nov '17

Mark, thanks for taking care of this!! Unfortunately, it does not seem to work correctly, yet. For strings, as in your pyloader01.sql test (see below), the used/inserted default value appears to include the single-quotes "'" form the SQL syntax --- I assume you approved those by accident --- and for integers "strange values" are inserted; see test sql/test/BugTracker-2017/Tests/python_loader_clobbers_default_with_null.Bug-6464.sql Best, Stefan ----- On Nov 13, 2017, at 5:47 PM, Mark Raasveldt commits+m.raasveldt=cwi.nl(a)monetdb.org wrote: > Changeset: 4303f7489624 for MonetDB > URL: https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4303f7489624 > Modified Files: > sql/backends/monet5/Tests/pyloader01.sql > sql/backends/monet5/Tests/pyloader01.stable.out > sql/backends/monet5/UDF/pyapi/emit.c > sql/backends/monet5/UDF/pyapi/pyloader.c > sql/include/sql_catalog.h > sql/server/rel_updates.c > Branch: Jul2017 > Log Message: > > Properly respect DEFAULT values in the Python loader. > > > diffs (145 lines): > > diff --git a/sql/backends/monet5/Tests/pyloader01.sql > b/sql/backends/monet5/Tests/pyloader01.sql > --- a/sql/backends/monet5/Tests/pyloader01.sql > +++ b/sql/backends/monet5/Tests/pyloader01.sql > @@ -1,7 +1,7 @@ > > START TRANSACTION; > > -CREATE TABLE mytable(a DOUBLE, d int, s STRING); > +CREATE TABLE mytable(a DOUBLE, d int, s STRING DEFAULT 'hello'); > > CREATE LOADER myfunc() LANGUAGE PYTHON { > _emit.emit({'a':42,'d':1}) > @@ -23,10 +23,10 @@ SELECT name,func,mod,language,type,side_ > > > -- there is a reason for this, functions with 0, 1, 2 and 3+ arguments are > handled differently. > +COPY LOADER INTO mytable FROM myfunc(); > COPY LOADER INTO mytable FROM myfunc3(46, 'asdf', 3.2); > COPY LOADER INTO mytable FROM myfunc2(45, 'asdf'); > COPY LOADER INTO mytable FROM myfunc1(44); > -COPY LOADER INTO mytable FROM myfunc(); > > SELECT * FROM mytable; > > diff --git a/sql/backends/monet5/Tests/pyloader01.stable.out > b/sql/backends/monet5/Tests/pyloader01.stable.out > --- a/sql/backends/monet5/Tests/pyloader01.stable.out > +++ b/sql/backends/monet5/Tests/pyloader01.stable.out > @@ -56,11 +56,11 @@ Ready. > % sys.mytable, sys.mytable, sys.mytable # table_name > % a, d, s # name > % double, int, clob # type > -% 24, 1, 5 # length > +% 24, 1, 7 # length > +[ 42, 1, "'hello'" ] > [ 46, 4, "hello" ] > -[ 45, 3, NULL ] > -[ 44, 2, NULL ] > -[ 42, 1, NULL ] > +[ 45, 3, "'hello'" ] > +[ 44, 2, "'hello'" ] > #DROP TABLE mytable; > #DROP ALL LOADER myfunc; > #CREATE LOADER myfunc() LANGUAGE PYTHON { > diff --git a/sql/backends/monet5/UDF/pyapi/emit.c > b/sql/backends/monet5/UDF/pyapi/emit.c > --- a/sql/backends/monet5/UDF/pyapi/emit.c > +++ b/sql/backends/monet5/UDF/pyapi/emit.c > @@ -199,6 +199,7 @@ PyObject *PyEmit_Emit(PyEmitObject *self > > self->cols[self->ncols].b = COLnew(0, bat_type, 0, TRANSIENT); > self->cols[self->ncols].name = GDKstrdup(val); > + self->cols[self->ncols].def = NULL; > if (self->nvals > 0) { > // insert NULL values up until the current entry > for (ai = 0; ai < self->nvals; ai++) { > @@ -209,9 +210,9 @@ PyObject *PyEmit_Emit(PyEmitObject *self > goto wrapup; > } > } > - self->cols[i].b->tnil = 1; > - self->cols[i].b->tnonil = 0; > - BATsetcount(self->cols[i].b, self->nvals); > + self->cols[self->ncols].b->tnil = 1; > + self->cols[self->ncols].b->tnonil = 0; > + BATsetcount(self->cols[self->ncols].b, self->nvals); > } > self->ncols++; > } > @@ -337,14 +338,21 @@ PyObject *PyEmit_Emit(PyEmitObject *self > self->cols[i].b->tnonil = 1 - self->cols[i].b->tnil; > } > } else { > + void* nill_value = ATOMnil(self->cols[i].b->ttype); > + void* default_value = self->cols[i].def ? > + self->cols[i].def : > + nill_value; > for (ai = 0; ai < (size_t)el_count; ai++) { > - if (BUNappend(self->cols[i].b, ATOMnil(self->cols[i].b->ttype), > + if (BUNappend(self->cols[i].b, > + default_value, > 0) != GDK_SUCCEED) { > goto wrapup; > } > } > - self->cols[i].b->tnil = 1; > - self->cols[i].b->tnonil = 0; > + if (BATatoms[self->cols[i].b->ttype].atomCmp(default_value, nill_value) == > 0) { > + self->cols[i].b->tnil = 1; > + self->cols[i].b->tnonil = 0; > + } > } > BATsetcount(self->cols[i].b, self->nvals + el_count); > } > diff --git a/sql/backends/monet5/UDF/pyapi/pyloader.c > b/sql/backends/monet5/UDF/pyapi/pyloader.c > --- a/sql/backends/monet5/UDF/pyapi/pyloader.c > +++ b/sql/backends/monet5/UDF/pyapi/pyloader.c > @@ -146,6 +146,9 @@ PYFUNCNAME(PyAPIevalLoader)(Client cntxt > assert(i < pci->retc); > cols[i].name = GDKstrdup(*((char **)n->data)); > n = n->next; > + assert(n); > + cols[i].def = n->data; > + n = n->next; > cols[i].b = > COLnew(0, getBatType(getArgType(mb, pci, i)), 0, TRANSIENT); > cols[i].b->tnil = 0; > diff --git a/sql/include/sql_catalog.h b/sql/include/sql_catalog.h > --- a/sql/include/sql_catalog.h > +++ b/sql/include/sql_catalog.h > @@ -599,6 +599,7 @@ extern node *find_sql_func_node(sql_sche > typedef struct { > BAT *b; > char* name; > + void* def; > } sql_emit_col; > > #endif /* SQL_CATALOG_H */ > diff --git a/sql/server/rel_updates.c b/sql/server/rel_updates.c > --- a/sql/server/rel_updates.c > +++ b/sql/server/rel_updates.c > @@ -1173,7 +1173,7 @@ table_column_types(sql_allocator *sa, sq > } > > static list * > -table_column_names(sql_allocator *sa, sql_table *t) > +table_column_names_and_defaults(sql_allocator *sa, sql_table *t) > { > node *n; > list *types = sa_list(sa); > @@ -1181,6 +1181,7 @@ table_column_names(sql_allocator *sa, sq > if (t->columns.set) for (n = t->columns.set->h; n; n = n->next) { > sql_column *c = n->data; > append(types, &c->base.name); > + append(types, c->def); > } > return types; > } > @@ -1577,7 +1578,7 @@ copyfromloader(mvc *sql, dlist *qname, s > return NULL; > } > ((sql_subfunc*) import->f)->res = table_column_types(sql->sa, t); > - ((sql_subfunc*) import->f)->colnames = table_column_names(sql->sa, t); > + ((sql_subfunc*) import->f)->colnames = > table_column_names_and_defaults(sql->sa, t); > > for (n = t->columns.set->h; n; n = n->next) { > sql_column *c = n->data; > _______________________________________________ > checkin-list mailing list > checkin-list(a)monetdb.org > https://www.monetdb.org/mailman/listinfo/checkin-list -- | Stefan.Manegold(a)CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ | Science Park 123 (L321) | | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |

1 0

MonetDB Integration Question
by David Broneske 13 Nov '17

13 Nov '17

Dear developers of MonetDB, I hope you are the right recipients of this mail that can help us in getting some more insights into MonetDB’s Code. Currently, me and my student (Florian) want to integrate our index structure Elf (www.elf.ovgu.de <http://www.elf.ovgu.de/>) into MonetDB as a proof of concept and to show its competitiveness to fast main-memory scans. However, we’ve got a hard time to understand some part of the code — we hope that you could help us with this. While the kernel (gdk) is well documented, we hardly find any documentation that may help us in answering the following questions: Which function takes care of filling the BATs when inserting into a table (i.e., sql_table/sql_rel)? COPY INTO creates a MAL-procedure copy_into, which is preparing the copy, but does not finally execute the copy. Which function is executed for this? Regarding ChangeSets: what is dset and nelm used for? Any pointer or explanation for these questions would be great! Regards, David and Florian M.Sc. David Broneske Otto-von-Guericke-Universität Magdeburg Department of Technical and Business Information Systems <http://wwwiti.cs.uni-magdeburg.de/> Databases and Software Engineering <http://wwwiti.cs.uni-magdeburg.de/iti_db/index_en.php> P.O. Box 4120, D-39016 Magdeburg, Germany Office: Building 29, Room112 Tel: +49 391 67-52994 <tel:+49 391 67-52994> Fax: +49 391 67-12020 <fax:+49 391 67-12020>

2 1

Announcement: New Jul2017-SP2 Bugfix release of MonetDB suite
by Sjoerd Mullender 26 Oct '17

26 Oct '17

The MonetDB team at CWI/MonetDB BV is pleased to announce the Jul2017-SP2 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/>. Jul 2017-SP2 bugfix release (11.27.9) MonetDB Common * A serious bug, possibly resulting in database corruption, having to do with appending data to a string BAT was fixed. Bug Fixes * 4017: server crashes when executing particular loopback query in embedded python * 6207: identifier ambiguous when grouping and selecting the same column twice * 6239: Incorrect profiling * 6261: New handling of delta tables hurts badly reusage of bats * 6287: should the CORR function return some numeric type that allows fractions? * 6321: Two-column aggregation on join result extremely slow. * 6335: Sqlitelogictest crash in complex SQL query * 6343: MERGE TABLE issue: unable to find * 6348: Interference of procedure/table name * 6350: Carriage return and form feed in TEXT fields are returned as 'r' and 'f' in jdbcclient and ResultSets * 6352: Scope resolution problem (sqlsmith) * 6353: implicit NULL value not propagated in distributed/remote query * 6374: Wrong answer from merge table after content changes * 6379: Table UDF: SEGV raised when invoking a non existing function * 6380: unable to create new databases from clean installation * 6381: Parser misses error messages in conditional * 6382: Can't set JSON fields via PreparedStatement * 6384: crash when setting a wrong listenaddr * 6385: AGGREGATE UDFs with more than 2 parameters incorrectly processed * 6386: Unexpected error from server for query with long floats * 6387: Performance degradation on multi column sort * 6388: JDBC Connection via user voc produces errors when fetching certain meta data information * 6392: SELECT EXISTS (empty table) returns 'true' * 6395: BAT leak of scalar result sets * 6397: Isolation of generating functions not correct * 6398: Null Matches in outer join are not supported * 6399: UDF crashes when subquery and scalar values are passed as pameters * 6400: getCharacterStream() currently not supported * 6404: COPY INTO crashes if table has primary key or foreign key constraint * 6405: Compilation error if DISABLE_PARENT_HASH not defined * 6409: sqllogictest crash on aggregation query with NOT IN clause in HAVING clause * 6410: Sqlitelogictest crash on aggregation query with IN clause * 6411: Sqlitelogictest crash in aggregation query * 6412: Overflow in sys.epoch * 6413: Wrong answer for TPC-H Q17 * 6414: Using RPAD returns: could not allocate space * 6416: Sqlitelogictest crash in aggregation query with a NOT IN clause * 6417: Segfault encountered (sqlsmith) * 6418: Segfault in renaming (sqlsmith) * 6419: segfault in rel_optimizer (sqlsmith) * 6420: Assertion error in mergetable task (sqlsmith) * 6422: Another assertion error in rel_or (sqlsmith) * 6423: Dereference null pointer (sqlsmith) * 6424: Assertion error in rel_rename_expr (sqlsmith) * 6425: Assertion error in exp_bin (sqlsmith) * 6426: Assertion error in rel_find_exp_ (sqlsmith) * 6427: Assertion error in eq_typeswitchloop (sqlsmith) * 6428: Sqlitelogictest crash in aggregation query * 6430: Assertion raised in another eq_typeswitch error (sqlsmith) * 6431: Sqlitelogictest crash in aggregation query with a long having clause * 6432: Assertion error in exp_bin (sqlsmith) * 6433: Sqlitelogictest crash in complex SELECT query with IN operator * 6435: Sqlitelogictest crash in simple select query * 6437: System schemas "profiler" and "json" shouldn't be allowed to be dropped. * 6438: Implement functionality to enforce the restrict option in: DROP SCHEMA xyz RESTRICT; * 6440: Faulty plan generated. Query returns more rows than expected or existing in the view sys.tables.

1 0

IMPORTANT: serious possibility for database corruption
by Sjoerd Mullender 23 Oct '17

23 Oct '17

We just found (and fixed) a serious problem in the Jul2017 releases that can result in database corruption. So far we have only seen the corruption occur after a database (mserver5) restart. We have not yet seen a problem with a server that continues running (but unfortunately no guarantees). We will create a new release candidate with this bug fixed as soon as possible (that will be version 11.27.9, i.e. anything in the 11.27.X series older than this is affected). Currently known work around is to *not* restart the server, but keep it running, and creating a dump of the database using msqldump. This dump will then have to be restored into a fresh database in a server that is not affected by the bug (Dec2016 release or the upcoming Jul2017-SP2). -- Sjoerd Mullender

1 0

Announcement: New Jul2017-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 02 Aug '17

02 Aug '17

The MonetDB team at CWI/MonetDB BV is pleased to announce the Jul2017-SP1 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/>. Jul 2017-SP1 bugfix release Build Environment * The Debian and Ubuntu installers have been fixed: there was a file missing in the Jul2017 release. * Added a new RPM called MonetDB-selinux which provides the SELinux policy required to run MonetDB under systemd, especially on Fedora 26. * The Windows installers (*.msi files) are now created using the WiX Toolset. * The Windows binaries are now built using Visual Studio 2015. Because of this, you may need to install the Visual C++ Redistributable for Visual Studio 2015 before being able to run MonetDB. Merovingian * monetdbd was leaking open file descriptors to the mserver5 process it started. This has been fixed. MonetDB Common * Many functions in GDK are now annotated with the GCC attribute __warn_unused_result__ meaning that the compiler will issue a warning if the result of the function (usually an indication of an error) is not used. Bug Fixes * 6325: Merge table unusable in other connections * 6328: Transactional/multi-connection issues with merge tables * 6336: VALUES multiple inserts error * 6339: Mserver5 crashes on nested SELECT * 6340: sample operator takes effect after the execution of the query, expected before * 6341: MERGE TABLE issue: Cannot register * 6342: MERGE TABLE issue: hang * 6344: Spurious errors and assertions (SQLsmith) * 6375: MAL profiler truncates JSON objects larger than 8192 characters

1 0

Trying to make sense of multi-farm databases
by Eyal Rozenberg 21 Jul '17

21 Jul '17

Hello all, I've noticed a change introduced to the release version in Jun 2016 that I can't find a bugzilla bug or a detailed comment for, and I wish to understand a little better: multi-farm DBs, or multi-farm BAT buffer pools if you will. Questions: * Why do we have them? * Are BAT "roles", introduced with the patch for this issue, inherently relevant only with multiple DB farms? If not, why were they introduced at the same time and with the same changeset? * Is this considered a "good idea" design-wise, or perhaps an unfortunate necessity (e.g. due to client needs)? * When you create a new DB, is there a chance more than a single DB farm will be created when you haven't specifically requested this happen? Eyal

2 2

Announcement: New Jul2017 Feature release of MonetDB suite
by Sjoerd Mullender 18 Jul '17

18 Jul '17

The MonetDB team at CWI/MonetDB BV is pleased to announce the Jul2017 feature 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/>. Jul 2017 feature release MonetDB5 Server * The "sub" prefix of many functions, both at the MAL and the C level, has been removed. * Changed the interfaces of the AUTH* functions: pass values, not pointers to values. * Removed calc.setoid(). * group.subgroup is now called group.group if it is not refining a group. Both group.group and group.subgroup now also have variants with a candidate list. * The allocation schemes for MAL blocks and Variables has been turned into block-based. This reduces the number of malloc()/free() calls. . * Added a new server-side protocol implementation. The new protocol is backwards compatible with the old protocol. Clients can choose whether they want to use the old or the new protocol during the initial handshake with the server. The new protocol is a binary column-based protocol that is significantly faster than the old protocol when transferring large result sets. In addition, the new protocol supports compression using Snappy or LZ4. * Moved the sphinx extension module to its own repository. See https://dev.monetdb.org/hg/MonetDB-sphinx/. * Removed GSL module: it's now a separate (extension) package. See https://dev.monetdb.org/hg/MonetDB-gsl/. * The PCRE library is now optional for systems that support POSIX regular expressions. * Added 5 new sys schema tables: function_languages, function_types, key_types, index_types and privilege_codes. They are pre-loaded with static content and contain descriptive names for the various integer type and code values. See also sql/scripts/51_sys_schema_extension.sql Merovingian * Added handling of a dbextra property per database at the daemon level. The user can set the dbextra property for a database using the command: $ monetdb set dbextra=<path> <database> and the daemon will make sure to start the new server using the correct --dbextra parameter. Client Package * The mclient and msqldump programs lost compatibility with old mserver5 versions (pre 2014) which didn't have a "system" column in the sys.schemas table. * The mclient and msqldump programs lost compatibility with ancient mserver5 versions (pre 2011) which didn't have the sys.systemfunctions table. * Removed the "array" and "quick" functions from the mapi library. To be precise, the removed functions are: mapi_execute_array, mapi_fetch_field_array, mapi_prepare_array, mapi_query_array, mapi_quick_query, mapi_quick_query_array, and mapi_quick_response. * Added a more elaborate \help command for SQL expressions. MonetDB Common * Improved error checking in the logger code (dealing with the write-ahead log); changed return types a several functions from int to gdk_return (i.e., they now return GDK_SUCCEED or GDK_FAIL). The logger no longer calls GDKfatal on error. Instead the caller is responsible for dealing with errors. * BATsort may now create an order index as a by product. * Quantile calculations now use the order index if available (and use BATsort otherwise, producing an order index). * Quantiles calculate a position in the sorted column. If this position is not an integer, we now choose the nearest position, favoring the lower if the distance to the two adjacent positions is equal (round down to nearest integer). * Removed function BATprintf. Use BATprint or BATprintcolumns instead. * Removed BATsave from the list of exported functions. * Replaced BBPincref/BBPdecref with BBPfix/BBPunfix for physical reference count and BBPretain/BBPrelease for logical reference count maintenance. * Removed automatic conversion of 32-bit OIDs to 64 bits on 64-bit architectures. * Removed functions OIDbase() and OIDnew(). * Removed talign field from BAT descriptor. * BATappend now takes an optional (NULL if not used) candidate list for the to-be-appended BAT. * New function BATkeyed(BAT *b) that determines (possibly using a hash table) whether all values in b are distinct. SQL * Made the operator precedence of % equal to those of * and /. All three are evaluated from left to right. * Removed table sys.connections. It was a remnant of an experimental change that had already been removed in 2012. * Protect against runaway profiler events If you hit a barrier block during profiling, the JSON event log may quickly become unwieldy. Event production is protected using a high water mark, which ensures that never within the single execution of MAL block the instruction causes excessive event records. Bug Fixes * 3465: Request: add support for CREATE VIEW with ORDER BY clause * 3545: monetdb commands don't work with -h -P -p options (locally and remotely) * 3996: select * from sys.connections always returns 0 rows. Expected to see at least one row for the active connection. * 6187: Nested WITH queries not supported * 6225: Order of evaluation of the modulo operator * 6289: Crashes and hangs with remote tables * 6292: Runaway SQL optimizer in too many nested operators * 6310: Name resolution error (sqlsmith) * 6312: Object not found in LIMIT clause (sqlsmith) * 6313: Null type resolution in disjunction fails (sqlsmith) * 6319: Server crash on LATERAL (sqlsmith) * 6322: Crash on disjunction with LIMIT (sqlsmith) * 6323: Deadlock calling sys.bbp() * 6324: Sqlitelogictest crash in a IN query (8th) * 6327: The daemon does not respect the actual name of the mserver5 executable * 6330: Sqlitelogictest crash on a complex SELECT query * 6331: sys.statistics column "nils" always contains 0. Expected a positive value for columns that have one or more nils/NULLs * 6332: Sqlitelogictest crash related to an undefined MAL function

3 3

Re: MonetDB: default - Support LIMIT in scalar expressions
by Lefteris 12 Jul '17

12 Jul '17

maybe we could also support FIRST() and LAST() https://www.monetdb.org/bugzilla/show_bug.cgi?id=6333 On Wed, Jul 12, 2017 at 11:22 AM, Martin Kersten <commits+mk=cwi.nl(a)monetdb.org> wrote: > Changeset: 718758b70621 for MonetDB > URL: https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=718758b70621 > Modified Files: > sql/server/sql_parser.y > Branch: default > Log Message: > > Support LIMIT in scalar expressions > Picking a single element from a table is now supported using > LIMIT (and SAMPLE) in SET and UPDATE subqueries > > set v =(select * from tbl limit 1); > > > diffs (21 lines): > > diff --git a/sql/server/sql_parser.y b/sql/server/sql_parser.y > --- a/sql/server/sql_parser.y > +++ b/sql/server/sql_parser.y > @@ -772,7 +772,7 @@ set_statement: > append_string(l, $2 ); > append_symbol(l, $4 ); > $$ = _symbol_create_list( SQL_SET, l); } > - | set column_commalist_parens '=' subquery > + | set column_commalist_parens '=' subquery_with_orderby > { dlist *l = L(); > append_list(l, $2); > append_symbol(l, $4); > @@ -2919,7 +2919,7 @@ assignment: > append_symbol(l, $3 ); > append_string(l, $1); > $$ = _symbol_create_list( SQL_ASSIGN, l); } > - | column_commalist_parens '=' subquery > + | column_commalist_parens '=' subquery_with_orderby > { dlist *l = L(); > append_symbol(l, $3); > append_list(l, $1); > _______________________________________________ > checkin-list mailing list > checkin-list(a)monetdb.org > https://www.monetdb.org/mailman/listinfo/checkin-list

2 2

Re: MonetDB: Jul2017 - Initialize sys.argv, because tensorflow requi...
by Panagiotis Koutsourakis 22 Jun '17

22 Jun '17

Hello developers, Taking the opportunity from this commit, I wanted to initiate a discussion with respect the executable names inside the code. A few weeks ago I faced a problem when using the configure options --program-prefix and --program-suffix, that change the executable names. The problem was that the name mserver5 was hard coded and the daemon could not find the actual executable. I see two possible solutions: 1. Implement a mechanism that make a note in the monetdb_config.h 2. Implement a run time mechanism to compute the relevant file names. Solution #1 is probably a bit more difficult because the prefix/suffix transformation of the file names happens during the installation. Solution #2 is already partially implemented in the daemon (see the function get_bin_path in the file mutils.c), but will probably need to be generalized somehow. Comments? Ideas? Best, Panos. Mark Raasveldt @ 2017-06-15 13:22 GMT: > Changeset: 44e0bc7dab59 for MonetDB > URL: http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=44e0bc7dab59 > Modified Files: > sql/backends/monet5/UDF/pyapi/pyapi.c > Branch: Jul2017 > Log Message: > > Initialize sys.argv, because tensorflow requires this. > > > diffs (20 lines): > > diff --git a/sql/backends/monet5/UDF/pyapi/pyapi.c b/sql/backends/monet5/UDF/pyapi/pyapi.c > --- a/sql/backends/monet5/UDF/pyapi/pyapi.c > +++ b/sql/backends/monet5/UDF/pyapi/pyapi.c > @@ -1425,9 +1425,16 @@ PYFUNCNAME(PyAPIprelude)(void *ret) { > MT_lock_init(&queryLock, "query_lock"); > MT_lock_set(&pyapiLock); > if (!pyapiInitialized) { > +#ifdef IS_PY3K > + wchar_t* program = Py_DecodeLocale("mserver5", NULL); > + wchar_t* argv[] = { program }; > +#else > + char* argv[] = {"mserver5"}; > +#endif > str msg = MAL_SUCCEED; > PyObject *tmp; > Py_Initialize(); > + PySys_SetArgvEx(1, argv, 0); > _import_array(); > msg = _connection_init(); > if (msg != MAL_SUCCEED) { > _______________________________________________ > checkin-list mailing list > checkin-list(a)monetdb.org > https://www.monetdb.org/mailman/listinfo/checkin-list

5 4