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

check existence of external names for SQL functions/procedures at creation time #2753

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

Comments

@monetdb-team
Copy link

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

Date: 2010-12-13 07:59:04 +0100
From: @mlkersten
To: SQL devs <>
Version: 11.1.1 (Mar2011) [obsolete]
CC: @njnes

Last updated: 2011-03-28 17:31:35 +0200

Comment 15339

Date: 2010-12-13 07:59:04 +0100
From: @mlkersten

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Build Identifier:

When you define a PROCEDURE or FUNCTION using an external name, the system should check if the corresponding name can be resolved at definition time. (ako reference constraint)

Reproducible: Always

Steps to Reproduce:

create procedure dummy(vid int) external dummy.p;
call dummy(1);

Actual Results:

sql>create procedure dummy(vid int) external name dummy.p;
operation successful
sql>call dummy(1);
TypeException:user.s1_1[3]:'dummy.p' undefined in: _5:any := dummy.p(_4:int)
SQLException:SQLengine:Program contains errors

Expected Results:

sql>create procedure dummy(vid int) external name dummy.p;
SQL error: external name not bound
sql>call dummy(1);
SELECT: no such unary operator 'dummy(tinyint)'

Comment 15606

Date: 2011-03-18 17:07:17 +0100
From: @njnes

checks for module and function name are done. Type checking is left too the call time.

Comment 15638

Date: 2011-03-28 17:31:35 +0200
From: @sjoerdmullender

The Mar2011 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