Date: 2020-07-09 18:45:47 +0200
From: jpastuszek
To: GDK devs <>
Version: 11.37.7 (Jun2020)

Last updated: 2020-07-27 09:30:14 +0200

Comment 27896

Date: 2020-07-09 18:45:47 +0200
From: jpastuszek

After migrating from Apr2019-SP1 to Jun2020 (patched with patch from Bug #6922) when selecting data by timestamp column with WHERE statement on the timestamp I get only rows for timestamps just before midnight.

If the query for timestamp column was done against the base table (I use merge tables normally) with no WHERE statement and with ORDER BY statement the data returned by the first query will become correct (fixed).

After some digging I figured out that the "imprints" data files are not migrated to the new timestamp format. Looks like full scan query updates the "imprints" data.
As a workaround I have removed all ".timprints" files corresponding to "timestamp" type of BAT and that resolved the issue for me.

Comment 27899

Date: 2020-07-10 09:11:07 +0200
From: MonetDB Mercurial Repository <>

Changeset 79da4596fddd made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.

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

Changeset description:

Destroy index structures when upgrading a BAT to a new format.
This fixes bug #6923.