Changeset: 12fad67aeda1 for MonetDB
URL: https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=12fad67aeda1
Removed Files:
        ChangeLog.Jun2020
        clients/ChangeLog.Jun2020
        clients/mapilib/ChangeLog.Jun2020
        clients/odbc/ChangeLog.Jun2020
        common/stream/ChangeLog.Jun2020
        debian/libmonetdb-stream13.install
        debian/libmonetdb20.install
        debian/libmonetdbe0.install
        design.txt
        gdk/ChangeLog.Jun2020
        geom/ChangeLog.Jun2020
        misc/ChangeLog.Jun2020
        misc/selinux/ChangeLog.Jun2020
        monetdb5/ChangeLog.Jun2020
        sql/ChangeLog.Jun2020
        testing/ChangeLog.Jun2020
        tools/merovingian/ChangeLog.Jun2020
Branch: monetdbe-proxy
Log Message:

Merge with default.


diffs (truncated from 37874 to 300 lines):

diff --git a/.hgtags b/.hgtags
--- a/.hgtags
+++ b/.hgtags
@@ -781,3 +781,5 @@ bb157905ecb86908dcfb112d102a8c6152557b5d
 1e3bd8cd485a0880a7557aa5307e986a210a1e00 Jun2020_SP1_release
 bb157905ecb86908dcfb112d102a8c6152557b5d Jun2020_SP1_release
 94231c85384d893701beeeb69996f57c70fade4d Oct2020_root
+017e44827765fb819d31faefcdf9066dfe593f04 Oct2020_1
+017e44827765fb819d31faefcdf9066dfe593f04 Oct2020_release
diff --git a/ChangeLog-Archive b/ChangeLog-Archive
--- a/ChangeLog-Archive
+++ b/ChangeLog-Archive
@@ -1,6 +1,30 @@
 # DO NOT EDIT THIS FILE -- MAINTAINED AUTOMATICALLY
 # This file contains past ChangeLog entries
 
+* Mon Aug 10 2020 Ying Zhang <y.zh...@cwi.nl> - 11.39.1-20201006
+- Finished a first version of the new monitoring function
+  user_statistics(), which is only intended for the DBAs.
+  For each database user who has logged in during the current mserver5
+  session, it returns
+  "username": login name of the database user,
+  "querycount": the number of queries this user has executed since his/her
+      first login,
+  "totalticks": the total execution time (in microsecond) of the queries ran
+      by this user,
+  "maxquery": the query with the longest execution time (if two queries have
+      the same execution time, the newer overwrites the older),
+  "maxticks": the execution time of the 'maxquery' (in microsecond),
+  "started": the start timestamp of the 'maxquery',
+  "finished": the finish timestamp of the 'maxquery'.
+
+* Wed Jun 10 2020 Sjoerd Mullender <sjo...@acm.org> - 11.39.1-20201006
+- Removed support for LiDAR data, that is the SQL procedures
+  sys.lidarattach, sys.lidarload, and sys.lidarexport.
+
+* Thu Apr  2 2020 Martin Kersten <m...@cwi.nl> - 11.39.1-20201006
+- The sys.queue() has been turned into a circular buffer to allow for
+  inspection of both active, paused and recently executed queries.
+
 * Mon Apr 20 2020 Sjoerd Mullender <sjo...@acm.org> - 11.37.1-20200511
 - A new system to deal with debug output has been implemented.  There is
   now an option --dbtrace to mserver5 that takes a file argument to which
diff --git a/ChangeLog.Jun2020 b/ChangeLog.Jun2020
deleted file mode 100644
--- a/ChangeLog.Jun2020
+++ /dev/null
@@ -1,3 +0,0 @@
-# ChangeLog file for devel
-# This file is updated with Maddlog
-
diff --git a/ChangeLog.Oct2020 b/ChangeLog.Oct2020
--- a/ChangeLog.Oct2020
+++ b/ChangeLog.Oct2020
@@ -1,27 +1,3 @@
 # ChangeLog file for devel
 # This file is updated with Maddlog
 
-* Mon Aug 10 2020 Ying Zhang <y.zh...@cwi.nl>
-- Finished a first version of the new monitoring function
-  user_statistics(), which is only intended for the DBAs.
-  For each database user who has logged in during the current mserver5
-  session, it returns
-  "username": login name of the database user,
-  "querycount": the number of queries this user has executed since his/her
-      first login,
-  "totalticks": the total execution time (in microsecond) of the queries ran
-      by this user,
-  "maxquery": the query with the longest execution time (if two queries have
-      the same execution time, the newer overwrites the older),
-  "maxticks": the execution time of the 'maxquery' (in microsecond),
-  "started": the start timestamp of the 'maxquery',
-  "finished": the finish timestamp of the 'maxquery'.
-
-* Wed Jun 10 2020 Sjoerd Mullender <sjo...@acm.org>
-- Removed support for LiDAR data, that is the SQL procedures
-  sys.lidarattach, sys.lidarload, and sys.lidarexport.
-
-* Thu Apr  2 2020 Martin Kersten <m...@cwi.nl>
-- The sys.queue() has been turned into a circular buffer to allow for
-  inspection of both active, paused and recently executed queries.
-
diff --git a/MonetDB.spec b/MonetDB.spec
--- a/MonetDB.spec
+++ b/MonetDB.spec
@@ -97,7 +97,7 @@ Group: Applications/Databases
 License: MPLv2.0
 URL: https://www.monetdb.org/
 BugURL: https://bugs.monetdb.org/
-Source: 
https://www.monetdb.org/downloads/sources/Jun2020-SP1/%{name}-%{version}.tar.bz2
+Source: 
https://www.monetdb.org/downloads/sources/Oct2020/%{name}-%{version}.tar.bz2
 
 # The Fedora packaging document says we need systemd-rpm-macros for
 # the _unitdir and _tmpfilesdir macros to exist; however on RHEL 7
@@ -844,6 +844,160 @@ fi
 %postun -p /sbin/ldconfig
 
 %changelog
+* Tue Oct 06 2020 Sjoerd Mullender <sjo...@acm.org> - 11.39.1-20201006
+- Rebuilt.
+- BZ#3553: All schema access to ubiquitous functions
+- BZ#3815: Incorrect results when expression contains implicit
+  float/integer conversions
+- BZ#6415: Date arithmetic types are inconsistent
+- BZ#6814: provide native implementations for scalar functions
+  sys.degrees(rad) and sys.radians(deg)
+- BZ#6843: function sys.getcontent(url) always returns "Feature not
+  supported"
+- BZ#6857: remove not implemented aggregate function json.output(js json)
+- BZ#6870: Missing bulk operators
+- BZ#6910: SQLancer query: 'bat.append' undefined
+- BZ#6930: SQLancer crash on join with coalesce
+- BZ#6931: Allow EDITOR to be used for the current command in mclient
+- BZ#6935: Wrong result when dividing interval by literal float
+- BZ#6937: Lost the microsecond precisions
+- BZ#6938: Segmentation fault in MalOptimizer
+- BZ#6939: Error in optimizer multiplex when selecting
+  profiler.getlimit() or wlc.clock() or wlc.tick() or wlr.clock()
+  or wlr.tick()
+- BZ#6941: SELECT queries on remote table fail when using LIKE in WHERE
+  conditions
+- BZ#6943: JSON parser is too permissive
+- BZ#6948: msqldump with Empty BLOBs cannot be imported
+- BZ#6949: Loosing timing precision
+- BZ#6950: redundant/replicated code line in gdk/gdk_hash.c
+- BZ#6951: Use a different naming scheme for MAL blocks
+- BZ#6954: FILTER functions no longer find their implementation
+- BZ#6955: ROUND(DECIMAL, PRECISION) gives incorrect result with
+  non-scalar precision parameter
+- BZ#6960: implementation of log(arg1,arg2) function is not compliant
+  with the SQL standard, arguments are switched
+- BZ#6962: "SELECT * FROM ids LIMIT 1" produces: exp_bin: !ERROR: Could
+  not find %173.id
+- BZ#6964: Table returning function: Cannot access column descriptor
+- BZ#6965: Crash when using distinct on the result of a table returning
+  function
+- BZ#6974: Oct2020-branch cannot attach and load FITS files
+- BZ#6976: Oct2020: default dbfarm cannot be started
+- BZ#6978: Oct2020: d shows empty result in schema created by include
+  sql script
+- BZ#6979: timestamp add integer
+- BZ#6980: Oct2020: wrong mel definition for str.epilogue
+
+* Mon Aug 31 2020 Pedro Ferreira <pedro.ferre...@monetdbsolutions.com> - 
11.39.1-20201006
+- sql: Made general logarithm function log(x,base) compliant with the SQL
+  standard, by swapping the input parameters.
+  Instead of log(x,base), now is log(base,x).
+
+* Thu Aug 20 2020 Sjoerd Mullender <sjo...@acm.org> - 11.39.1-20201006
+- monetdb5: The settings for specifying how mserver5 should listen to "The
+  Internet" have been overhauled.  See the manual for details.  In
+  brief, mapi_autosense, mapi_ipv6 and mapi_open are gone.  If
+  mapi_listenaddr equals "localhost" or "all", we listen to both IPv4
+  and IPv6 (if available), if "127.0.0.1" or "0.0.0.0", we listen to
+  IPv4 only, if "::1" or "::" we listen to IPv6 only.  The first of
+  each pair is loopback interface only, the second is all interfaces.
+  If mapi_listenaddr is "none", then no IP port is opened, you need to
+  use a UNIX domain socket.  If mapi_port is 0, we let the operating
+  system choose a free port (like mapi_autosense).  Default behavior
+  has not changed.
+
+* Mon Aug 10 2020 Ying Zhang <y.zh...@cwi.nl> - 11.39.1-20201006
+- MonetDB: Finished a first version of the new monitoring function
+  user_statistics(), which is only intended for the DBAs.
+  For each database user who has logged in during the current mserver5
+  session, it returns
+  "username": login name of the database user,
+  "querycount": the number of queries this user has executed since his/her
+      first login,
+  "totalticks": the total execution time (in microsecond) of the queries ran
+      by this user,
+  "maxquery": the query with the longest execution time (if two queries have
+      the same execution time, the newer overwrites the older),
+  "maxticks": the execution time of the 'maxquery' (in microsecond),
+  "started": the start timestamp of the 'maxquery',
+  "finished": the finish timestamp of the 'maxquery'.
+
+* Thu Jul 23 2020 Pedro Ferreira <pedro.ferre...@monetdbsolutions.com> - 
11.39.1-20201006
+- sql: Removed compatibility between interval types and other numeric types in
+  favor for a more strict SQL standard compliance. This means operations
+  between temporal types and other numeric types such as INT and
+  DECIMAL are no longer possible, instead use interval types.
+  e.g. SELECT date '2020-01-01' + 1; now gives the error. Instead do:
+  SELECT date '2020-01-01' + interval '1' day; if 1 was meant to be a
+  day interval.
+  Setting an interval variable such as the session's current timezone
+  with a number e.g. SET current_timezone = 1; is no longer possible.
+  Instead do SET current_timezone = interval '1' hour;
+  Casting between interval and other numeric types is no longer possible
+  as well, because they are not compatible.
+- sql: Because of incompatibilities this change may create, if an user intents
+  to convert a numeric value to an interval, the multiplication function
+  can be used in the form: <numeric value> * interval '1' <interval length>
+  e.g. 10 * interval '1' second = interval '10' second.
+  As for the other way around, the 'EPOCH' option was added to the extract
+  syntax. This option returns the number of milliseconds since the UNIX
+  epoch 1970-01-01 00:00:00 UTC for date, timestamp and time values (it
+  can be negative). Meanwhile, for day and second intervals, it returns the
+  total number of milliseconds on the interval. As a side note, the 'EPOCH'
+  option is not available for month intervals, because this conversion is
+  not transparent for this type.
+
+* Thu Jul 23 2020 Pedro Ferreira <pedro.ferre...@monetdbsolutions.com> - 
11.39.1-20201006
+- sql: Removed obsolete json.output(json) function.
+
+* Thu Jul 23 2020 Pedro Ferreira <pedro.ferre...@monetdbsolutions.com> - 
11.39.1-20201006
+- sql: Removed obsolete sys.getContent(url) function.
+
+* Thu Jul 23 2020 Sjoerd Mullender <sjo...@acm.org> - 11.39.1-20201006
+- MonetDB: Removed support for LiDAR data, that is the SQL procedures
+  sys.lidarattach, sys.lidarload, and sys.lidarexport.
+
+* Thu Jul 23 2020 Pedro Ferreira <pedro.ferre...@monetdbsolutions.com> - 
11.39.1-20201006
+- sql: Removed '@' syntax used to refer into a variable in a query. It
+  was a non-standard method, which was replaced by a schema addition to
+  variables. Variables in the global scope now have schema. All default
+  global variables are set under schema "sys". However variables
+  inside PSM don't have a schema, because there are no transaction
+  semantics inside PSM at the moment.
+- sql: Removed declared variables and tables from the global scope. They were
+  transaction agnostic and incompatible with the SQL standard, i.e. they
+  are valid exclusively under PSM (e.g. functions, procedures and
+  triggers).
+- sql: Scoping semantics were added for both variables and tables. Variables
+  with the same name at a query are now resolved under the following
+  precedence rules:
+    1. Tables, Views and CTEs at the FROM clause.
+    2. Variable declared in the body of function/procedure, i.e. local
+       variable.
+    3. Function/procedure parameter.
+    4. Variable from the global scope.
+  Tables with the same name now have the following precedence rules at a
+  SQL query:
+    1. Table declared in the body of function/procedure, ie local table.
+    2. Temporary table.
+    3. Table from the current session schema.
+  This means the query: SELECT * FROM "keys"; will list keys from
+  temporary tables instead of persisted ones, because "keys" table
+  is available for both "sys" and "tmp" schemas.
+- sql: The table returning function "var" was extended with more details
+  about globally declared variables, namely their schema, type and
+  current value.
+
+* Thu Jul 23 2020 Martin Kersten <m...@cwi.nl> - 11.39.1-20201006
+- MonetDB: The sys.queue() has been turned into a circular buffer to allow for
+  inspection of both active, paused and recently executed queries.
+
+* Thu Jul 23 2020 Martin Kersten <m...@cwi.nl> - 11.39.1-20201006
+- sql: Extended the system monitor with a table-returning function
+  user_statistics() which keeps some statistics for each SQL user, e.g. the
+  user's query count, total time spent, and maximal query seen.
+
 * Thu Jul 23 2020 Sjoerd Mullender <sjo...@acm.org> - 11.37.11-20200723
 - Rebuilt.
 - BZ#6917: Decimal parsing fails
@@ -1298,7 +1452,6 @@ fi
 - BZ#6779: Using Windows Messages translation for errno error codes.
 - BZ#6780: Wrong value of the rank function
 - BZ#6781: Insert after index creation crash
-- BZ#6782: JDBC IsValid(int) does not reset lastquerytimeout on server
 - BZ#6783: AVG changes scale of its results
 - BZ#6784: function sys.isauuid(string) should return false if string
   value cannot be converted to a UUID
diff --git a/clients/ChangeLog.Jun2020 b/clients/ChangeLog.Jun2020
deleted file mode 100644
--- a/clients/ChangeLog.Jun2020
+++ /dev/null
@@ -1,3 +0,0 @@
-# ChangeLog file for clients
-# This file is updated with Maddlog
-
diff --git a/clients/Tests/MAL-signatures.stable.out 
b/clients/Tests/MAL-signatures.stable.out
--- a/clients/Tests/MAL-signatures.stable.out
+++ b/clients/Tests/MAL-signatures.stable.out
@@ -6175,6 +6175,10 @@ stdout of test 'MAL-signatures` in direc
 [ "batmtime",  "epoch",        "command 
batmtime.epoch(X_1:bat[:timestamp]):bat[:int] ",       
"MTIMEseconds_since_epoch_bulk;",       ""      ]
 [ "batmtime",  "epoch",        "command 
batmtime.epoch(X_1:bat[:lng]):bat[:timestamp] ",       
"MTIMEtimestamp_frommsec_bulk;",        ""      ]
 [ "batmtime",  "epoch",        "command 
batmtime.epoch(X_1:bat[:int]):bat[:timestamp] ",       
"MTIMEtimestamp_fromsecond_bulk;",      ""      ]
+[ "batmtime",  "epoch_ms",     "command 
batmtime.epoch_ms(X_1:bat[:date]):bat[:lng] ", 
"MTIMEdate_extract_epoch_ms_bulk;",     ""      ]
+[ "batmtime",  "epoch_ms",     "command 
batmtime.epoch_ms(X_1:bat[:daytime]):bat[:lng] ",      
"MTIMEdaytime_extract_epoch_ms_bulk;",  ""      ]
+[ "batmtime",  "epoch_ms",     "command 
batmtime.epoch_ms(X_1:bat[:lng]):bat[:lng] ",  
"MTIMEmsec_extract_epoch_ms_bulk;",     ""      ]
+[ "batmtime",  "epoch_ms",     "command 
batmtime.epoch_ms(X_1:bat[:timestamp]):bat[:lng] ",    
"MTIMEtimestamp_extract_epoch_ms_bulk;",        ""      ]
 [ "batmtime",  "hours",        "command 
batmtime.hours(X_1:bat[:daytime]):bat[:int] ", 
"MTIMEdaytime_extract_hours_bulk;",     ""      ]
 [ "batmtime",  "hours",        "command 
batmtime.hours(X_1:bat[:lng]):bat[:int] ",     "MTIMEsql_hours_bulk;", ""      ]
 [ "batmtime",  "hours",        "command 
batmtime.hours(X_1:bat[:timestamp]):bat[:int] ",       
"MTIMEtimestamp_hours_bulk;",   ""      ]
@@ -8939,6 +8943,10 @@ stdout of test 'MAL-signatures` in direc
 [ "mtime",     "epoch",        "command mtime.epoch(X_1:timestamp):int ",      
"MTIMEseconds_since_epoch;",    ""      ]
 [ "mtime",     "epoch",        "command mtime.epoch(X_1:lng):timestamp ",      
"MTIMEtimestamp_frommsec;",     ""      ]
 [ "mtime",     "epoch",        "command mtime.epoch(X_1:int):timestamp ",      
"MTIMEtimestamp_fromsecond;",   ""      ]
+[ "mtime",     "epoch_ms",     "command mtime.epoch_ms(X_1:date):lng ",        
"MTIMEdate_extract_epoch_ms;",  ""      ]
+[ "mtime",     "epoch_ms",     "command mtime.epoch_ms(X_1:daytime):lng ",     
"MTIMEdaytime_extract_epoch_ms;",       ""      ]
+[ "mtime",     "epoch_ms",     "command mtime.epoch_ms(X_1:lng):lng ", 
"MTIMEmsec_extract_epoch_ms;",  ""      ]
+[ "mtime",     "epoch_ms",     "command mtime.epoch_ms(X_1:timestamp):lng ",   
"MTIMEtimestamp_extract_epoch_ms;",     ""      ]
 [ "mtime",     "hours",        "command mtime.hours(X_1:daytime):int ",        
"MTIMEdaytime_extract_hours;",  ""      ]
 [ "mtime",     "hours",        "command mtime.hours(X_1:lng):int ",    
"MTIMEsql_hours;",      ""      ]
 [ "mtime",     "hours",        "command mtime.hours(X_1:timestamp):int ",      
"MTIMEtimestamp_hours;",        ""      ]
diff --git a/clients/Tests/MAL-signatures.stable.out.int128 
b/clients/Tests/MAL-signatures.stable.out.int128
--- a/clients/Tests/MAL-signatures.stable.out.int128
+++ b/clients/Tests/MAL-signatures.stable.out.int128
@@ -8744,6 +8744,10 @@ stdout of test 'MAL-signatures` in direc
_______________________________________________
checkin-list mailing list
checkin-list@monetdb.org
https://www.monetdb.org/mailman/listinfo/checkin-list

Reply via email to