Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Mar2018]: mclient's default timing mode should (again) be "none" rather than "clock" #6537

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2018-02-08 09:40:36 +0100
From: @drstmane
To: clients devs <>
Version: 11.27.11 (Jul2017-SP3)

Last updated: 2018-03-29 15:39:09 +0200

Comment 26177

Date: 2018-02-08 09:40:36 +0100
From: @drstmane

as an alternative (or addition?) to feature request / bug #6536:

mclient's default timing mode should (again) be "none" rather than "clock"

much like feature request / bug #6536 this is mainly to avoid that the default timing output compromises/invalidates the format of mclient's output formatters csv, tab, xml.

Comment 26193

Date: 2018-02-14 09:56:42 +0100
From: MonetDB Mercurial Repository <>

Changeset 01645d98a71b made by Stefan Manegold Stefan.Manegold@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=01645d98a71b

Changeset description:

mclient: make timermode "none" the default (again)
as per feature request / bug #6537

Comment 26197

Date: 2018-02-14 10:17:30 +0100
From: @drstmane

Fixed / implemented by changeset 01645d98a71b .

Comment 26305

Date: 2018-03-29 15:39:09 +0200
From: @sjoerdmullender

The Mar2018 version has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant