- developers-list - monetdb.org

Parameters in bind function
by Narendra Pradeep 01 Aug '16

01 Aug '16

Hello everyone , I am trying to understand the MAL statements for joining three tables . On which I came across bind function in MAL statement . I have a table lineitem with l_quantity in it . So what does the following statements means 1 ) ( X_94:bat[:oid,:oid] ,X_95:bat[:oid,:int] ) := sql.bind(X_4,"sys","lineitem","l_quantity",2,0,4); 2 ) (X_96:bat[:oid,:oid] ,X_97:bat[:oid,:int] ) := sql.bind(X_4,"sys","lineitem","l_quantity",2,1,4); what does the 5 th and 6 th argument means ?

1 0

does cracking implemented in monetdb
by Narendra Pradeep 28 Jul '16

28 Jul '16

My questions are 1) Does cracking implemented in monetdb ? 2) Which file contains the code for cracking in source ? 3) Can we trace cracking and find whether query reads record from disc or the cracked columns ? Thanks in advance. regards , Pradeep.

2 1

Re: MonetDB: Jun2016 - Trace BATs should be reset before the next TR...
by Sjoerd Mullender 28 Jul '16

28 Jul '16

This is not correct. I made the exact opposite change in changeset 080dcfcb43e4 in order to fix memory leaks. That worked, but now those leaks are back. Clearly another solution is needed. On 28/07/16 00:31, Martin Kersten wrote: > Changeset: 25c896ae6a53 for MonetDB > URL: http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=25c896ae6a53 > Modified Files: > monetdb5/mal/mal_profiler.c > Branch: Jun2016 > Log Message: > > Trace BATs should be reset before the next TRACE call > BBPunfix was slipped in, while it should simply be a BATclear. > > > diffs (36 lines): > > diff --git a/monetdb5/mal/mal_profiler.c b/monetdb5/mal/mal_profiler.c > --- a/monetdb5/mal/mal_profiler.c > +++ b/monetdb5/mal/mal_profiler.c > @@ -761,19 +761,19 @@ clearTrace(void) > return; /* not initialized */ > } > /* drop all trace tables */ > - BBPunfix(TRACE_id_event->batCacheid); > - BBPunfix(TRACE_id_time->batCacheid); > - BBPunfix(TRACE_id_pc->batCacheid); > - BBPunfix(TRACE_id_thread->batCacheid); > - BBPunfix(TRACE_id_ticks->batCacheid); > - BBPunfix(TRACE_id_rssMB->batCacheid); > - BBPunfix(TRACE_id_tmpspace->batCacheid); > - BBPunfix(TRACE_id_inblock->batCacheid); > - BBPunfix(TRACE_id_oublock->batCacheid); > - BBPunfix(TRACE_id_minflt->batCacheid); > - BBPunfix(TRACE_id_majflt->batCacheid); > - BBPunfix(TRACE_id_nvcsw->batCacheid); > - BBPunfix(TRACE_id_stmt->batCacheid); > + BBPclear(TRACE_id_event->batCacheid); > + BBPclear(TRACE_id_time->batCacheid); > + BBPclear(TRACE_id_pc->batCacheid); > + BBPclear(TRACE_id_thread->batCacheid); > + BBPclear(TRACE_id_ticks->batCacheid); > + BBPclear(TRACE_id_rssMB->batCacheid); > + BBPclear(TRACE_id_tmpspace->batCacheid); > + BBPclear(TRACE_id_inblock->batCacheid); > + BBPclear(TRACE_id_oublock->batCacheid); > + BBPclear(TRACE_id_minflt->batCacheid); > + BBPclear(TRACE_id_majflt->batCacheid); > + BBPclear(TRACE_id_nvcsw->batCacheid); > + BBPclear(TRACE_id_stmt->batCacheid); > TRACE_init = 0; > MT_lock_unset(&mal_contextLock); > initTrace(); > _______________________________________________ > checkin-list mailing list > checkin-list(a)monetdb.org > https://www.monetdb.org/mailman/listinfo/checkin-list > -- Sjoerd Mullender

1 0

Instrumentation in monetdb
by Narendra Pradeep 22 Jul '16

22 Jul '16

eello everyone , How can I get instumemtation in monetdb ? I need thedetails like planning time , execution time for each MAL statement in monetdb . Is there any command for it ? regards , Pradeep

2 1

Fwd: Monet php_mapi.inc
by Mark Raasveldt 22 Jul '16

22 Jul '16

> Begin forwarded message: > > From: Alberto Ferrari <aferrari(a)starconnecting.com> > Subject: Monet php_mapi.inc > Date: 21 July 2016 at 17:22:34 GMT+2 > To: Mark Raasveldt <m.raasveldt(a)cwi.nl> > > Hi Mark, > (about https://dev.monetdb.org/hg/MonetDB/file/tip/clients/php/lib/php_mapi.inc) > > I've been using the "php_mapi.inc" in my php web application in the > last few months. So I modified the "php_mapi.inc" to a php class, > which is more efficient and correct (to me). > I am not registered in the Mercurial repo, so , if you (or somebody) > are interested on my "class" version, I can send you attached, and > then feel free to publish it, if you want. > Just tell me. > > regards > Alberto Ferrari.

2 1

Announcement: New Jun2016-SP1 Bugfix release of MonetDB suite
by Sjoerd Mullender 22 Jul '16

22 Jul '16

The MonetDB team at CWI/MonetDB BV is pleased to announce the Jun2016-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/>. Jun 2016-SP1 bugfix release . * Lots of memory leaks have been plugged across the whole system. Java Module * Corrected PROCEDURE_TYPE output value of method DatabaseMetaData.getProcedures(). It used to return procedureReturnsResult. Now it returns procedureNoResult. Corrected ORDINAL_POSITION output value of method DatabaseMetaData.getProcedureColumns(). It used to start with 0, but as procedures do not return a result value it now starts with 1 for all the procedure arguments, as defined by the JDBC API. * Improved output of method DatabaseMetaData.getProcedures(). The REMARKS column now contains the procedure definition as stored in sys.functions.func. The SPECIFIC_NAME column now contains the procedure unique identifier as stored in sys.functions.id. This allows the caller to retrieve the specific overloaded procedure which has the same name, but different arguments. Also improved output of method DatabaseMetaData.getProcedureColumns(). The SPECIFIC_NAME column now contains the procedure unique identifier as stored in sys.functions.id. This allows the caller to retrieve the proper arguments of the specific overloaded procedure by matching the SPECIFIC_NAME value. * Improved output of method DatabaseMetaData.getFunctions(). The REMARKS column now contains the function definition as stored in sys.functions.func. The SPECIFIC_NAME column now contains the function unique identifier as stored in sys.functions.id. This allows the caller to retrieve the specific overloaded function which has the same name, but different arguments. Also improved output of method DatabaseMetaData.getFunctionColumns(). The SPECIFIC_NAME column now contains the function unique identifier as stored in sys.functions.id. This allows the caller to retrieve the proper arguments of the specific overloaded function by matching the SPECIFIC_NAME value. Bug Fixes * 4014: KILL signal * 4021: Analyze query does not escape input [security] * 4026: JDBC driver incorrectly converts TINYINT fields to String instead of an integer type. * 4028: inputs not the same size * 4031: mclient doesn't accept - argument to refer to stdin * 4032: no decimal places after update. ODBC driver * 4035: SQL Function call bug * 4036: Possible sql_catalog corruption due to unclean backuped tail

1 0

Tracking query & user information during execution
by Playfair, Daniel 19 Jul '16

19 Jul '16

Hi MonetDB Developers, I'm working to add intra-query checkpoint/restart functionality to MonetDB as part of my PhD work. I have a partial implementation and have completed the component for transmitting intermediate values (to a separate middleware), and have a plan that I think should work for replay. Most of these modifications are in the runMALsequence function in the mal interpreter. Currently my implementation transmits all intermediates and I'm having some difficulty on the component to selectively transmit selected intermediates. I was hoping you might be able answer some of my questions to point me in the right direction on this aspect. I intend for the actual checkpoint planning to be performed on the query plan graphs in an offline step. This relates to one of my problems - The MAL variable names for intermediates seem to change accross executions. 1. Is there a way to have these identifiers be consistent? 2. What factors determine the values they take? Secondly, I am having difficulty with tracking/accessing information about the user, original SQL query, and current MAL operation step to be able to tag the transmitted intermediates with sufficient data for the middleware & load balancer to be able to relate this to a user session & query. I believe this should be accessible via 3. How can I access this information from the inputs available in runMALsequence (in mal_interpreter.c) I believe it's probably somewhere in the mal stack, instruction record, or client structs, but I am having difficulty here. Any help and input would be greatly appreciated. Many thanks, ~ Daniel.

1 0

Announcement: New Jun2016 Feature release of MonetDB suite
by Sjoerd Mullender 23 Jun '16

23 Jun '16

The MonetDB team at CWI/MonetDB BV is pleased to announce the Jun2016 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/>. Jun 2016 feature release MonetDB5 Server * Extended the storage() table producing function to also accept storage([schemaname [, tablename [, columnname]]]) * The :bat[:oid,:any] type descriptor has been turned into its columnar version :bat[:any] * Converted the *.mal scripts into *.malC versions to prepare for removal of the mserver console. * Removed functions mat.hasMoreElements, mat.info, mat.mergepack, mat. newIterator, mat.project, mat.pack2, mat.sortReverse, mat.sort, and mat.slice. * Removed grouped aggregate functions from the aggr module in which the groups were indicated by the head column of the bat to be aggregated. Use the interface with a separate group bat instead. * The server now stops executing a query when the client disconnects. * Removed algebra.join. Use algebra.subjoin instead. * Removed algebra.antijoin. Use algebra.subantijoin or algebra.subthetajoin instead. * The MAL function 'leftfetchjoin' is renamed to its relational algebra version 'projection' * The generic property handling scheme has been removed. It was used in just a few places, for widely different purposes and contained cruft. * Removed functions str.iconv and str.codeset. Internally, strings are always in UTF-8 encoding, so we can't allow code set conversions. * Removed algebra.like with a BAT argument. Use algebra.likesubselect instead. * Removed algebra.leftjoin. Use algebra.subleftjoin or algebra.leftfetchjoin instead. * Removed algebra.tdiff and algebra.tinter. * Removed algebra.sample. Use sample.subuniform instead. * Removed algebra.select. Use algebra.subselect instead. * Removed algebra.revert. * Removed bat.order and bat.orderReverse functions. * Changed client.getUsers to return two bats, one with the user id and one with the user name. * Implemented algebra.subdiff and algebra.subinter. * Removed algebra.tdifference and algebra.tintersect. * Removed algebra.tunion. Build Environment * A new package MonetDB-lidar (Fedora) or libmonetdb5-server-lidar (Debian/Ubuntu) has been created to work with LiDAR data. * Implemented a systemd configuration file for a monetdbd.service on systems that support it (Fedora, newer Ubuntu). Client Package * The Ruby client is now in a separate repository (http://dev.monetdb.org/hg/monetdb-ruby) and released independently. Geom Module * The geom module has been completely overhauled. Types are now specified as GEOMETRY(POINT) instead of POINT, old functions have been removed, new ones introduced. However, even with all the changes, a database upgrade should still be possible (as always, make a backup first). MonetDB Common * Removed BATconst. Use BATconstant instead. * Changed BATconstant. It now has a new first argument with the seqbase for the head column. * Removed BATmmap. It was no longer used. * BUNdelete and BATdel don't accept a foce argument and only allow deleting values that have not yet been committed. BUNdelete exchanges the deleted value with the last value (if the deleted value isn't the last value). BATdel compacts the BAT by shifting values after the deleted values up. The list of to-be-deleted values in BATdel must be sorted and unique. * Removed BUNreplace from list of exported functions. It wasn't used, and there is still BUNinplace and void_inplace that do more-or-less the same thing. * Changed BATderiveHeadProps to BATderiveTailProps (and it now works on the tail column). * Removed unused functions BATalpha, BATdelta, and BATprev. * Removed function VIEWcombine. Use BATdense instead. * Removed "left" parameter from BUNinplace. It wasn't used since the BAT it works on is dense headed. * Created function BATdense to easily create a [void,void] BAT with specified seqbases for head and tail and a count. * Removed function BATmark. When all head columns are dense, BATmark basically only created a new [void,void] BAT. * Renamed BATsubsort to BATsort. * Removed "sub" from the names of the function BATsubselect, BATthetasubselect, BATsubcross, BATsubleftjoin, BATsubouterjoin, BATsubthetajoin, BATsubsemijoin, BATsubdiff, BATsubjoin, BATsubbandjoin, BATsubrangejoin, and BATsubunique. * Removed BATsubleftfetchjoin: it was not used. * Removed BATcross1. Use BATsubcross instead. * Removed all versions of the SORTloop macro. * Removed Batkdiff. Use BATsubdiff instead. * Removed BATselect. Use BATsubselect instead. * Removed BATsemijoin. Use BATsubsemijoin instead. * Removed BATjoin. Use BATsubjoin instead. * Removed BATleftjoin. Use BATsubleftjoin or BATproject instead. * Removed BATleftfetchjoin. Use BATproject instead. * Removed BUNins from the list of exported functions. * Removed legacy functions BATuselect and BATuselect_. * Removed legacy functions BATantijoin, BATbandjoin, BATouterjoin, BATrangejoin, and BATthetajoin. * Removed function BATrevert. * BATordered now works on the TAIL column. * Removed obsolete functions BATorder() and BATorder_rev(). * Implemented BATsubdiff which returns a list of OIDs (sorted, i.e. usable as candidate list) of tuples in the left input whose value does not occur in the right input. * Removed function BATkintersect. It wasn't used anymore. It's functionality can be obtained by using BATsubsemijoin. * Removed the function BATkunion. Java Module * Fixed problem in DatabaseMetaData.getUDTs() when it was called with types parameter filled. It used to throw SQException with message: SELECT: identifier 'DATA_TYPE' unknown. Now it returns the UDTs which match the provided array of data types. * Implemented MonetDatabaseMetaData.supportsConvert() and MonetDatabaseMetaData.supportsConvert(int fromType, int toType) methods. It used to always return false. Now it returns true for the supported conversions. This fixes Bug 3460. * ResultSet.setFetchSize(): added a dummy implementation to get rid of the SQLFeatureNotSupportedException. In MonetDB, it does not make sense to set the fetch size of a result set. If one really wants to set the fetch size, one should use Statement.setFetchSize() instead. * Fixed resource leak in ResultSetMetaData. It created and cached a ResultSet object for each column but never closed the ResultSet objects. * Corrected DatabaseMetaData methods which accept a catalog filter argument. Those methods will now filter the results on the specified catalog name, whereas previously the catalog filter argument was ignored. * Corrected output of column KEY_SEQ of DatabaseMetaData methods: getPrimaryKeys(), getImportedKeys(), getExportedKeys() and getCrossReference(). It now starts at 1 instead of 0 previously. * Corrected DatabaseMetaData.getSchemas() by returning 2 instead of 3 columns. * Improved DatabaseMetaData.getColumns() by returning two additional columns: IS_AUTOINCREMENT and IS_GENERATEDCOLUMN. * Improved DatabaseMetaData.getTypeInfo(). It now returns better information on LITERAL_PREFIX, LITERAL_SUFFIX, CREATE_PARAMS, CASE_SENSITIVE, FIXED_PREC_SCALE and MAXIMUM_SCALE for some data types. Also the returned rows are now ordered by DATA_TYPE, TYPE_NAME, PRECISION as required by the specs. Also corrected output column names "searchable" into "SEARCHABLE" and "MAXIMUM SCALE" into "MAXIMUM_SCALE" to match the JDBC specification. * Corrected DatabaseMetaData.getPseudoColumns(). It used to return 12 empty rows. Now it returns no rows as MonetDB does not have pseudo columns. * Implemented method DatabaseMetaData.getClientProperties(). It used to always return a resultset with 4 completely empty rows. It now returns a resultset with the possible connection properties. * Implemented method DatabaseMetaData.getUDTs(). It used to return an empty resultset. Now it returns the User Defined Types such as inet, json, url and uuid. * Corrected the returned table types in DatabaseMetaData.getTableTypes(). It now returns all 10 table types (as stored in sys.table_types) instead of the previously 8 hardcoded table types. For old MonetDB servers which do not have the sys.table_types table, the old behavior is retained. * Implemented methods DatabaseMetadata.getProcedures() and DatabaseMetadata.getProcedureColumns(). They used to return an empty resultset. Now they return the expected Procedures and ProcedureColumns. Also getProcedureColumns() now returns a resultset with all 20 columns instead of 13 columns previously. * Method getFunctionColumns() in DatabaseMetadata used to throw an SQLException: getFunctionColumns(String, String, String, String) is not implemented. This method is now implemented and returns a resultset. * Method getFunctions() in DatabaseMetadata used to throw an SQLException: SELECT: no such column 'functions.sql' This has been corrected. It now returns a resultset as requested. * The resultsets of DatabaseMetadata methods now no longer return a value for the *_CAT columns as MonetDB does not support Catalogs. * Fixed a memory leak in MonetDatabaseMetaData.java for a static cache which kept references to closed Connection objects. * Improved JdbcClient program when presenting query data to console. It used to send an SQL catalog query for each query result column which slowed down the interactive response considerably. These additional SQL catalog queries have been eliminated. * Corrected MonetResultSet.getObject(String columnName). It no longer throws a NullPointerException in cases where internally a MonetVirtualResultSet is used. * Fixed Connection.isValid(): this method should never attempt to close the connection, even if an error has occurred. SQL * Disallow GRANT <some-user> TO <role-or-use>. Only explicitly created roles can be granted. * Extended grantable schema privileges: when a user is granted the "sysadmin" role, the user now hcan not only create schemas, but also drop schemas. * Introduced COPY INTO/ COPY FROM global privileges. These privileges allows other users than 'monetdb' to be granted the privileges to use the MonetDB bulk data loading/exporting features, i.e., COPY FROM <file> and COPY INTO <file>. Bug Fixes * 2407: Merovingian: allow binds to given ip/interface * 2815: No SRID support * 3361: constants as MAL function parameters prevent intermediate reuse * 3374: UNIQUE constraint does not set tkey property on the corresponding BAT * 3460: incomplete implementation of JDBC driver supportsConvert(), supportsConvert(int fromType, int toType) methods in MonetDatabaseMetaData.java * 3711: JDBC connection using jdbcclient.jar is very slow * 3877: MonetDBLite should allow close then re-open databases? without restarting R * 3911: Invalid connect() call in 'redirect' mode * 3920: query with DISTINCT and correlated scalar subquery in SELECT list causes Assertion failure and crash of mserver5 * 3927: COUNT( distinct my_clob ) , QUANTILE( my_double , number ) fails in dev build * 3956: MonetDBLite unable to execute LIMIT 1 statement * 3972: Drastic Memory leak of 600GBs while generating plan for Query with 25 joins * 3974: Prepared statement rel_bin.c:2378: rel2bin_project: Assertion `0' failed. * 3975: Suspicious code in store_manager() on exit path * 3978: SQL returns TypeException 'aggr.subcorr' undefined for sys.corr function * 3980: JOIN with references on both sides crashes mserver * 3981: Incorrect LEFT JOIN when FROM clause contains nested subqueries * 3983: Creation of a Foreign Key which partially maps to a primary key is accepted without a warning * 3984: Multiple paths in the .profile * 3985: ruby-monetdb-sql gem fails for negative timezone offset (USA, etc.) * 3987: Segfault on malformed csv import * 3991: MonetDBLite feature request: default monetdb.sequential to FALSE on windows * 3994: MonetDBLite dbDisconnect with shutdown=TRUE freezes the console on windows * 3995: NullPointerException when calling getObject() * 3997: calling scalar functions sys.isaUUID(str) or sys.isaUUID(uuid) fail * 3999: length() returns wrong length for strings which have spaces at the end of the string * 4010: RELEASE SAVEPOINT after ALTER TABLE crashes mserver5 * 4011: sys.sessions.user column always shows 'monetdb' * 4013: GDKextendf does not free up memory when it fails due to insufficient resources * 4015: Daemon crashes on database release command

1 0

Announcement: New Jun2016 Feature release of MonetDB suite
by Sjoerd Mullender 23 Jun '16

23 Jun '16

The MonetDB team at CWI/MonetDB BV is pleased to announce the Jun2016 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/>. Jun 2016 feature release MonetDB5 Server * Extended the storage() table producing function to also accept storage([schemaname [, tablename [, columnname]]]) * The :bat[:oid,:any] type descriptor has been turned into its columnar version :bat[:any] * Converted the *.mal scripts into *.malC versions to prepare for removal of the mserver console. * Removed functions mat.hasMoreElements, mat.info, mat.mergepack, mat. newIterator, mat.project, mat.pack2, mat.sortReverse, mat.sort, and mat.slice. * Removed grouped aggregate functions from the aggr module in which the groups were indicated by the head column of the bat to be aggregated. Use the interface with a separate group bat instead. * The server now stops executing a query when the client disconnects. * Removed algebra.join. Use algebra.subjoin instead. * Removed algebra.antijoin. Use algebra.subantijoin or algebra.subthetajoin instead. * The MAL function 'leftfetchjoin' is renamed to its relational algebra version 'projection' * The generic property handling scheme has been removed. It was used in just a few places, for widely different purposes and contained cruft. * Removed functions str.iconv and str.codeset. Internally, strings are always in UTF-8 encoding, so we can't allow code set conversions. * Removed algebra.like with a BAT argument. Use algebra.likesubselect instead. * Removed algebra.leftjoin. Use algebra.subleftjoin or algebra.leftfetchjoin instead. * Removed algebra.tdiff and algebra.tinter. * Removed algebra.sample. Use sample.subuniform instead. * Removed algebra.select. Use algebra.subselect instead. * Removed algebra.revert. * Removed bat.order and bat.orderReverse functions. * Changed client.getUsers to return two bats, one with the user id and one with the user name. * Implemented algebra.subdiff and algebra.subinter. * Removed algebra.tdifference and algebra.tintersect. * Removed algebra.tunion. Build Environment * A new package MonetDB-lidar (Fedora) or libmonetdb5-server-lidar (Debian/Ubuntu) has been created to work with LiDAR data. * Implemented a systemd configuration file for a monetdbd.service on systems that support it (Fedora, newer Ubuntu). Client Package * The Ruby client is now in a separate repository (http://dev.monetdb.org/hg/monetdb-ruby) and released independently. Geom Module * The geom module has been completely overhauled. Types are now specified as GEOMETRY(POINT) instead of POINT, old functions have been removed, new ones introduced. However, even with all the changes, a database upgrade should still be possible (as always, make a backup first). MonetDB Common * Removed BATconst. Use BATconstant instead. * Changed BATconstant. It now has a new first argument with the seqbase for the head column. * Removed BATmmap. It was no longer used. * BUNdelete and BATdel don't accept a foce argument and only allow deleting values that have not yet been committed. BUNdelete exchanges the deleted value with the last value (if the deleted value isn't the last value). BATdel compacts the BAT by shifting values after the deleted values up. The list of to-be-deleted values in BATdel must be sorted and unique. * Removed BUNreplace from list of exported functions. It wasn't used, and there is still BUNinplace and void_inplace that do more-or-less the same thing. * Changed BATderiveHeadProps to BATderiveTailProps (and it now works on the tail column). * Removed unused functions BATalpha, BATdelta, and BATprev. * Removed function VIEWcombine. Use BATdense instead. * Removed "left" parameter from BUNinplace. It wasn't used since the BAT it works on is dense headed. * Created function BATdense to easily create a [void,void] BAT with specified seqbases for head and tail and a count. * Removed function BATmark. When all head columns are dense, BATmark basically only created a new [void,void] BAT. * Renamed BATsubsort to BATsort. * Removed "sub" from the names of the function BATsubselect, BATthetasubselect, BATsubcross, BATsubleftjoin, BATsubouterjoin, BATsubthetajoin, BATsubsemijoin, BATsubdiff, BATsubjoin, BATsubbandjoin, BATsubrangejoin, and BATsubunique. * Removed BATsubleftfetchjoin: it was not used. * Removed BATcross1. Use BATsubcross instead. * Removed all versions of the SORTloop macro. * Removed Batkdiff. Use BATsubdiff instead. * Removed BATselect. Use BATsubselect instead. * Removed BATsemijoin. Use BATsubsemijoin instead. * Removed BATjoin. Use BATsubjoin instead. * Removed BATleftjoin. Use BATsubleftjoin or BATproject instead. * Removed BATleftfetchjoin. Use BATproject instead. * Removed BUNins from the list of exported functions. * Removed legacy functions BATuselect and BATuselect_. * Removed legacy functions BATantijoin, BATbandjoin, BATouterjoin, BATrangejoin, and BATthetajoin. * Removed function BATrevert. * BATordered now works on the TAIL column. * Removed obsolete functions BATorder() and BATorder_rev(). * Implemented BATsubdiff which returns a list of OIDs (sorted, i.e. usable as candidate list) of tuples in the left input whose value does not occur in the right input. * Removed function BATkintersect. It wasn't used anymore. It's functionality can be obtained by using BATsubsemijoin. * Removed the function BATkunion. Java Module * Fixed problem in DatabaseMetaData.getUDTs() when it was called with types parameter filled. It used to throw SQException with message: SELECT: identifier 'DATA_TYPE' unknown. Now it returns the UDTs which match the provided array of data types. * Implemented MonetDatabaseMetaData.supportsConvert() and MonetDatabaseMetaData.supportsConvert(int fromType, int toType) methods. It used to always return false. Now it returns true for the supported conversions. This fixes Bug 3460. * ResultSet.setFetchSize(): added a dummy implementation to get rid of the SQLFeatureNotSupportedException. In MonetDB, it does not make sense to set the fetch size of a result set. If one really wants to set the fetch size, one should use Statement.setFetchSize() instead. * Fixed resource leak in ResultSetMetaData. It created and cached a ResultSet object for each column but never closed the ResultSet objects. * Corrected DatabaseMetaData methods which accept a catalog filter argument. Those methods will now filter the results on the specified catalog name, whereas previously the catalog filter argument was ignored. * Corrected output of column KEY_SEQ of DatabaseMetaData methods: getPrimaryKeys(), getImportedKeys(), getExportedKeys() and getCrossReference(). It now starts at 1 instead of 0 previously. * Corrected DatabaseMetaData.getSchemas() by returning 2 instead of 3 columns. * Improved DatabaseMetaData.getColumns() by returning two additional columns: IS_AUTOINCREMENT and IS_GENERATEDCOLUMN. * Improved DatabaseMetaData.getTypeInfo(). It now returns better information on LITERAL_PREFIX, LITERAL_SUFFIX, CREATE_PARAMS, CASE_SENSITIVE, FIXED_PREC_SCALE and MAXIMUM_SCALE for some data types. Also the returned rows are now ordered by DATA_TYPE, TYPE_NAME, PRECISION as required by the specs. Also corrected output column names "searchable" into "SEARCHABLE" and "MAXIMUM SCALE" into "MAXIMUM_SCALE" to match the JDBC specification. * Corrected DatabaseMetaData.getPseudoColumns(). It used to return 12 empty rows. Now it returns no rows as MonetDB does not have pseudo columns. * Implemented method DatabaseMetaData.getClientProperties(). It used to always return a resultset with 4 completely empty rows. It now returns a resultset with the possible connection properties. * Implemented method DatabaseMetaData.getUDTs(). It used to return an empty resultset. Now it returns the User Defined Types such as inet, json, url and uuid. * Corrected the returned table types in DatabaseMetaData.getTableTypes(). It now returns all 10 table types (as stored in sys.table_types) instead of the previously 8 hardcoded table types. For old MonetDB servers which do not have the sys.table_types table, the old behavior is retained. * Implemented methods DatabaseMetadata.getProcedures() and DatabaseMetadata.getProcedureColumns(). They used to return an empty resultset. Now they return the expected Procedures and ProcedureColumns. Also getProcedureColumns() now returns a resultset with all 20 columns instead of 13 columns previously. * Method getFunctionColumns() in DatabaseMetadata used to throw an SQLException: getFunctionColumns(String, String, String, String) is not implemented. This method is now implemented and returns a resultset. * Method getFunctions() in DatabaseMetadata used to throw an SQLException: SELECT: no such column 'functions.sql' This has been corrected. It now returns a resultset as requested. * The resultsets of DatabaseMetadata methods now no longer return a value for the *_CAT columns as MonetDB does not support Catalogs. * Fixed a memory leak in MonetDatabaseMetaData.java for a static cache which kept references to closed Connection objects. * Improved JdbcClient program when presenting query data to console. It used to send an SQL catalog query for each query result column which slowed down the interactive response considerably. These additional SQL catalog queries have been eliminated. * Corrected MonetResultSet.getObject(String columnName). It no longer throws a NullPointerException in cases where internally a MonetVirtualResultSet is used. * Fixed Connection.isValid(): this method should never attempt to close the connection, even if an error has occurred. SQL * Disallow GRANT <some-user> TO <role-or-use>. Only explicitly created roles can be granted. * Extended grantable schema privileges: when a user is granted the "sysadmin" role, the user now hcan not only create schemas, but also drop schemas. * Introduced COPY INTO/ COPY FROM global privileges. These privileges allows other users than 'monetdb' to be granted the privileges to use the MonetDB bulk data loading/exporting features, i.e., COPY FROM <file> and COPY INTO <file>. Bug Fixes * 2407: Merovingian: allow binds to given ip/interface * 2815: No SRID support * 3361: constants as MAL function parameters prevent intermediate reuse * 3374: UNIQUE constraint does not set tkey property on the corresponding BAT * 3460: incomplete implementation of JDBC driver supportsConvert(), supportsConvert(int fromType, int toType) methods in MonetDatabaseMetaData.java * 3711: JDBC connection using jdbcclient.jar is very slow * 3877: MonetDBLite should allow close then re-open databases? without restarting R * 3911: Invalid connect() call in 'redirect' mode * 3920: query with DISTINCT and correlated scalar subquery in SELECT list causes Assertion failure and crash of mserver5 * 3927: COUNT( distinct my_clob ) , QUANTILE( my_double , number ) fails in dev build * 3956: MonetDBLite unable to execute LIMIT 1 statement * 3972: Drastic Memory leak of 600GBs while generating plan for Query with 25 joins * 3974: Prepared statement rel_bin.c:2378: rel2bin_project: Assertion `0' failed. * 3975: Suspicious code in store_manager() on exit path * 3978: SQL returns TypeException 'aggr.subcorr' undefined for sys.corr function * 3980: JOIN with references on both sides crashes mserver * 3981: Incorrect LEFT JOIN when FROM clause contains nested subqueries * 3983: Creation of a Foreign Key which partially maps to a primary key is accepted without a warning * 3984: Multiple paths in the .profile * 3985: ruby-monetdb-sql gem fails for negative timezone offset (USA, etc.) * 3987: Segfault on malformed csv import * 3991: MonetDBLite feature request: default monetdb.sequential to FALSE on windows * 3994: MonetDBLite dbDisconnect with shutdown=TRUE freezes the console on windows * 3995: NullPointerException when calling getObject() * 3997: calling scalar functions sys.isaUUID(str) or sys.isaUUID(uuid) fail * 3999: length() returns wrong length for strings which have spaces at the end of the string * 4010: RELEASE SAVEPOINT after ALTER TABLE crashes mserver5 * 4011: sys.sessions.user column always shows 'monetdb' * 4013: GDKextendf does not free up memory when it fails due to insufficient resources * 4015: Daemon crashes on database release command

1 0

(no subject)
by Narendra Pradeep 22 Jun '16

22 Jun '16

While coming across Monetdb source there are three structures which were used most often.They are MalBlkPtr mb MalStkPtr stk InstrPtr pci What are they meant for ? what is their initial value and when do they get initialized ? Thanks

1 0