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

Using RPAD returns: could not allocate space #6414

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

Using RPAD returns: could not allocate space #6414

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

Comments

@monetdb-team
Copy link

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

Date: 2017-10-09 09:59:49 +0200
From: Gatis Ozolins <<g.ozolins>>
To: SQL devs <>
Version: 11.27.5 (Jul2017-SP1)

Last updated: 2017-10-26 14:01:29 +0200

Comment 25685

Date: 2017-10-09 09:59:49 +0200
From: Gatis Ozolins <<g.ozolins>>

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build Identifier:

Error "could not allocate space" is received when using RPAD with length parameter = 0

Reproducible: Always

Steps to Reproduce:

SELECT RPAD('test', 0)

Actual Results:

SQL Error [HY001]: could not allocate space
java.sql.SQLException: could not allocate space

Expected Results:

NULL

Comment 25695

Date: 2017-10-12 09:21:36 +0200
From: MonetDB Mercurial Repository <>

Changeset 32f71cab2c3b 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=32f71cab2c3b

Changeset description:

GDKstrndup with size 0 should return an empty string, not no string.
This fixes bug #6414.
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