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

Inconsistent RDB$COLLATION_ID when restoring from 2.5 to 3.0 for same UDF [CORE6081] #6331

Open
firebird-automations opened this issue Jun 11, 2019 · 0 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @cincuranet

Steps:
1. Create empty database on 2.5.
2. Create this UDF:
DECLARE EXTERNAL FUNCTION BIGTIMESPAN_TO_STRING
BIGINT
RETURNS CSTRING(20) FREE_IT
ENTRY_POINT 'BigTimeSpanToString' MODULE_NAME 'Fast';
3. Backup the database using gbak.
4. Restore the database on 3.0 using gbak.
5. Check RDB$FUNCTION_ARGUMENTS.RDB$COLLATION_ID for the return argument. It's NULL.
5. Create the same UDF again (either new name or drop+create).
6. Check RDB$FUNCTION_ARGUMENTS.RDB$COLLATION_ID for the return argument again. It's non-NULL.

Same function, same declaration, different result.

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