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

Wrong Plan For BIGINT in debug Stored Procedure [CORE1352] #1771

Closed
firebird-automations opened this issue Jul 10, 2007 · 6 comments
Closed

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: maziar navahan (maziar1)

i have problem with Plan of BIGINT variable in stored procedure in ver 2.0.1

------------------------------

CREATE PROCEDURE with_bigint_type( the same code true debug in rev
...eclare variable z_pd_bed bigint
...
IF (z_BED IS NULL) THEN z_BED = 0;

in this line i get this plan for it
SELECT COUNT() FROM RDB$DATABASE WHERE ( cast(0 as numeric(0,0)) IS NULL)

seems is wrong

@firebird-automations
Copy link
Collaborator Author

Modified by: maziar navahan (maziar1)

Version: 2.1 Beta 2 [ 10190 ]

Version: 2.1 Beta 1 [ 10141 ] =>

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Sorry, but the ticket is completely unreadable.

@firebird-automations
Copy link
Collaborator Author

Commented by: maziar navahan (maziar1)

Sorry me For Bad English

For see this Problem in(Engine: Firebird ver 2.1 beta1) Try debug Stored Procedure with bigint type in parameter and Var

in Ibexpert in line with same below code (z_BED is BIGINT) :
IF (z_BED IS NULL) THEN z_BED = 0;

in plan view :
SELECT COUNT() FROM RDB$DATABASE WHERE ( cast(0 as numeric(0,0)) IS NULL)

i dont understand why in bigint type i see :(0 as numeric(0,0))
the same code in same version of Ibexpert for firebird 2.0.1 plan is :(0 as bigint)

is better comment ?

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

This has nothing to do with Firebird, as Firebird doesn't support SP debugging (yet) ! This feature is directly implemented by tools (like IBExpert) in the way that they *emulate* the SP processing locally as it would be performed by Firebird. Hence it's the problem in the 3rd party tool, not Firebird.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Open [ 1 ] => Closed [ 6 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 12532 ] => Firebird [ 14145 ]

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