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
NOT NULL constraint for procedure parameters and variables [CORE1316] #1735
Comments
Commented by: Sean Leyne (seanleyne) Alexander, You seem to be logging a large number of feature requests which have already been discussed and rejected (in the support list) or are not always appropriate (as in this case). I would suggest that you post a discussion message to the developer list before creating these entries. In this way, the requests can be publically discussed, and perhaps improved upon, before an entry is added to the tracker. |
Commented by: Alexander Tyutik (tut) Sorry. I started read developers list only a few months ago, so i haven't read discussion about this feature. In feature i will be more careful with requests like this... |
Commented by: Claudio Valderrama C. (robocop) The feature has been implemented by Adriano. This is the result of an isql session: SQL> create database 'mydearnull.fdb'; SQL> set term ^; The only improvement could be that in the first case, the message can say "validation error for parameter ID, ..." instead of "variable". |
Modified by: Claudio Valderrama C. (robocop)status: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 RC1 [ 10201 ] assignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @pcisarWorkflow: jira [ 12290 ] => Firebird [ 14796 ] |
Commented by: @pmakowski Q/A test ok |
Modified by: @pmakowskistatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Alexander Tyutik (tut)
Is related to QA265
Now we able to use domains in PSQL code and this is greate!
But what if we need to use same domain as NULLABLE in one case and as NOT NULL in other case?
It's very simple for tables, but for procedure parameters and variables we should create two diffirent domains or write manual checking.
As we already have such checking for domains i think it is possible to add equal checking for explicit declaration, such as:
DECLARE ID INTEGER NOT NULL;
OR
CREATE PROCEDURE GET_SOMETHING (
ID INTEGER NOT NULL,
...
The text was updated successfully, but these errors were encountered: