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

lower(name) clause in query causing "BATsubselect: invalid argument.." error #3287

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


Copy link

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

Date: 2013-05-18 02:08:59 +0200
From: Tim H. <<monetdb.bug.reporter>>
To: SQL devs <>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes

Last updated: 2013-07-03 08:48:00 +0200

Comment 18738

Date: 2013-05-18 02:08:59 +0200
From: Tim H. <<monetdb.bug.reporter>>

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31
Build Identifier:

[root ~] mclient -d testdb -u monetdb
Database: MonetDB v11.15.8 (unreleased)
sql>select name from "sys".users where lower(name) = 'monetdb';
GDK reported error.
BATsubselect: invalid argument: b must have a dense head.

Reproducible: Always

Steps to Reproduce:

  1. start with an empty database named testdb
  2. mclient -d testdb -u monetdb
  3. create user my_user with password 'p1' name 'User with role' schema "sys";
  4. select name from "sys".users where lower(name) = 'monetdb';

Actual Results:

GDK reported error.
BATsubselect: invalid argument: b must have a dense head.

Expected Results:

| name |
| monetdb |
| my_user |

I can delete the user my_user then re-run the problem query and it does not report an error.

Comment 18740

Date: 2013-05-18 16:47:50 +0200
From: MonetDB Mercurial Repository <>

Changeset 2fb3afea17e5 made by Niels Nes in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2fb3afea17e5

Changeset description:

fixed bug #3287, ie non void users bat.

Comment 18741

Date: 2013-05-18 16:49:10 +0200
From: @njnes

fixed in sql using extra mark

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

Successfully merging a pull request may close this issue.

None yet
1 participant