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

select fails when udf returning blob [CORE296] #627

Closed
firebird-automations opened this issue Mar 24, 2002 · 3 comments
Closed

select fails when udf returning blob [CORE296] #627

firebird-automations opened this issue Mar 24, 2002 · 3 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Claudio Valderrama C. (robocop)

Assigned to: Claudio Valderrama C. (robocop)

SFID: 534208#⁠
Submitted By: robocop

As reported by Ivan Prenosil and other person before:

select udf(<params>) from tbl;

will fail if the udf's return type is a blob. Problem
comes from METD that gives a zero length to blob
fields in UDFs. The correct length for blobs is a
quad, 8 bytes. In turn, METD_get_function() gets zero
because when a udf is defined, ddl.c:put_field()
doesn't send length information for blobs to DYN.

@firebird-automations
Copy link
Collaborator Author

Commented by: Alice F. Bird (firebirds)

Date: 2002-03-24 03:35
Sender: robocop
Logged In: YES
user_id=62823

Since put_field() is a routine shared by every metadata
definition function, it was much safer to have METD set 8
bytes for udf's params being blobs in the run-time
structure, since this size is fixed and constant.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 10320 ] => Firebird [ 14523 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant