-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
TYPE OF COLUMN in PSQL [CORE1356] #1774
Comments
Modified by: @cincuranetsummary: Oracle's %type for procedures => Oracle's '%type' for procedures |
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Commented by: @asfernandes I already started work on this and will propose in fb-architect soon. |
Commented by: @cincuranet Good to hear this. |
Commented by: @asfernandes Syntax: TYPE OF COLUMN <table or view name>.<column name> |
Modified by: @asfernandesissuetype: Improvement [ 4 ] => New Feature [ 2 ] summary: Oracle's '%type' for procedures => TYPE OF COLUMN in PSQL |
Modified by: @pcisarFix Version: 2.1 Beta 2 [ 10190 ] |
Commented by: @asfernandes No, Pavel, this is not Beta2. This is B3_0_Transition branch, and it requires ODS change, so it will be in next major release. But since I don't know if we'll have a major release before V3, I didn't marked the fix version. |
Modified by: @asfernandesFix Version: 2.1 Beta 2 [ 10190 ] => |
Modified by: @pcisarWorkflow: jira [ 12580 ] => Firebird [ 14200 ] |
Modified by: @asfernandesFix Version: 2.5 Alpha 1 [ 10224 ] |
Commented by: @asfernandes Documentation is in doc/sql.extensions/README.column_type_psql.txt |
Modified by: @pmakowskistatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @cincuranet
Is related to QA300
Oracle has nice feature that you can use use '%type' to specify type of parameter in procedure. For example:
id_ticket http://ticket.id%type;
so it's easy to use same type in procedure as in table. I know, we have now domains in procedures, but not everytime you create domain for column.
The text was updated successfully, but these errors were encountered: