[
https://issues.apache.org/jira/browse/CALCITE-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062012#comment-17062012
]
Julian Hyde commented on CALCITE-3726:
--------------------------------------
A sub-task means that it is a part of the parent task. So it's impossible for
the parent task to be fixed before all sub-tasks. Maybe you need to use a link
like 'related'?
The terms you use are misleading. You are not declaring a type, you are
creating an object of a particular type. I guess you are using a constructor.
Posting just a link as description isn't good enough. Give a simple use case.
You use a gerund - 'declaring' - which means that the sentence does not have a
subject. You don't say who the user is. You should make it clear who the user
is - the person writing SQL.
I'm sorry to be so hard on you. But when you implement a feature, a crucial
part of the task is to communicate with the community, and you failed in that.
Your description was utterly confusing to me. (Yes, I didn't read the code.
Because our users should not need to read the code.)
> Allow declaring type objects
> ----------------------------
>
> Key: CALCITE-3726
> URL: https://issues.apache.org/jira/browse/CALCITE-3726
> Project: Calcite
> Issue Type: New Feature
> Reporter: Ritesh
> Assignee: Ritesh
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.23.0
>
> Time Spent: 5h 40m
> Remaining Estimate: 0h
>
> [https://docs.oracle.com/cd/B19306_01/appdev.102/b14261/objects.htm#i7530]
> e.g. :
>
> {code:java}
> employee_typ(315, 'Francis', 'Logan', 'FLOGAN',
> '555.777.2222', '01-MAY-04', 'SA_MAN', 11000, .15, 101, 110,
> address_typ('376 Mission', 'San Francisco', 'CA', '94222'))
> {code}
> After an object type is defined and installed in the schema, you can use it
> to declare objects in any SQL block. For example, you can use the object type
> to specify the datatype of an attribute, column, variable, bind variable,
> record field, table element, formal parameter, or function result. At run
> time, instances of the object type are created; that is, objects of that type
> are instantiated. Each object can hold different values.
> Such objects follow the usual scope and instantiation rules. In a block or
> subprogram, local objects are instantiated when you enter the block or
> subprogram and cease to exist when you exit. In a package, objects are
> instantiated when you first reference the package and cease to exist when you
> end the database session.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
