Hello Dmitry,

Thursday, December 23, 2004, 4:19:29 AM, you wrote:

> "Claudio Valderrama C." <cvalde@...> wrote:
>>
>> If the proc doesn't have a suspend at all, then using it like a table is
> an
>> error. Probably will upset anyone, but what useful output can the
> developer
>> get now if he tries to select from a non-selectable stored proc. He will
> get
>> nothing without any explanations and without any hint the call syntax was
>> wrong. I tend to agree with stopping compilation here.

> Also agreed.

I also agree with Claudio.

>> Having additional metadata to signal the type of the procedure is fine for
>> me. It's a small change, it's easy to detect when creating or altering the
>> procedure and doesn't change the current behavior; it only provides more
>> information in system tables. I don't understand why people put too much
>> effort to resist that little enhancement.

> I support this idea, if nothing else (except the point mentioned above) is
> changed. I'm also ready to add RDB$PROCEDURE_TYPE to ODS11.

If adding the necessary logic to automatically populate that field
isn't much to implement, and that with FB2, the ODS is changing. Then
why not do it.

And, maybe add the CALL syntax in a future version of FB(I suppose a
feature request would have to be entered to remember it).

--
Best regards,
Daniel Rail
Senior Software Developer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)