Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).
What is the cause of this error? Or, where do we exceed a limit?
Solved
nesting level exceeded (limit 32)
+12- Superhero
- 136 replies
I want to set some role rights on a specific table but I keep getting this error:
Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).
What is the cause of this error? Or, where do we exceed a limit?
Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).
What is the cause of this error? Or, where do we exceed a limit?
Best answer by Anne Buit
Hi Hugo,
The cause of this might very well be a circular look-up reference. Check out the look-up table and look_up column for dagboek_id in the table dagboek. If there is a look-up configured, keep following down the chain. If you end up going in circles, you've found the problem.
Feel free to create a ticket for this issue. An error like this should not occur. There is a good chance this problem is resolved in the upcoming release but we'd like to check it out anyway.
View originalThe cause of this might very well be a circular look-up reference. Check out the look-up table and look_up column for dagboek_id in the table dagboek. If there is a look-up configured, keep following down the chain. If you end up going in circles, you've found the problem.
Feel free to create a ticket for this issue. An error like this should not occur. There is a good chance this problem is resolved in the upcoming release but we'd like to check it out anyway.
This topic has been closed for comments
+5Hi Hugo,
The cause of this might very well be a circular look-up reference. Check out the look-up table and look_up column for dagboek_id in the table dagboek. If there is a look-up configured, keep following down the chain. If you end up going in circles, you've found the problem.
Feel free to create a ticket for this issue. An error like this should not occur. There is a good chance this problem is resolved in the upcoming release but we'd like to check it out anyway.
The cause of this might very well be a circular look-up reference. Check out the look-up table and look_up column for dagboek_id in the table dagboek. If there is a look-up configured, keep following down the chain. If you end up going in circles, you've found the problem.
Feel free to create a ticket for this issue. An error like this should not occur. There is a good chance this problem is resolved in the upcoming release but we'd like to check it out anyway.
1 person likes this
+12- Superhero
- 136 replies
It was indeed a problem with the reference. Thanks for the help.
1 person likes this
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.