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.

Sign up for GitHub

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

Jump to bottom

FB Classic. Trigger's code changes doesn't affected in another connetions [CORE875] #1267

Closed
firebird-automations opened this issue Jul 27, 2006 · 5 comments
Closed

FB Classic. Trigger's code changes doesn't affected in another connetions [CORE875] #1267

firebird-automations opened this issue Jul 27, 2006 · 5 comments
Labels
affect-version: 1.5.3 component: engine priority: major resolution: wontfix type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Tkachenko Igor (mauzer_tim)

I change trigger's code in one connection, and then I try to fire trigger, I update record. If I update record at given connection, the new code executed, but if I update record at another connections, that was opened before trigger changing, the old code executed.
This oddity revealed in the Firebird Classic version 1.5.3. Client library has worked on WindowsXP machine, and DB server has worked on a Linux. I foreget version of Linux, and I will specify it later, if it will required.
@firebird-automations
Copy link
Collaborator Author

Modified by: Tkachenko Igor (mauzer_tim)

description: When I change trigger's code in one connection, and then I try to fire trigger, I update record. If I update record at given connection, the new code executed, but if I update record at another connections, that was opened before trigger changing, the old code executed.
This oddity revealed in the Firebird Classic version 1.5.3. Client library has worked on WindowsXP machine, and DB server has worked on a Linux. I foreget version of Linux, and I will specify it later, if it will required.

=>

I change trigger's code in one connection, and then I try to fire trigger, I update record. If I update record at given connection, the new code executed, but if I update record at another connections, that was opened before trigger changing, the old code executed.
This oddity revealed in the Firebird Classic version 1.5.3. Client library has worked on WindowsXP machine, and DB server has worked on a Linux. I foreget version of Linux, and I will specify it later, if it will required.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

This is perfectly "as designed". Please read Data Definition Guide, chapter "Altering and dropping procedures in use".

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11100 ] => Firebird [ 15116 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affect-version: 1.5.3 component: engine priority: major resolution: wontfix type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@firebird-automations