Fixed the error: Implementation limit exceeded #1228
Closed
+0
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gilsonjoanelo
force-pushed
the
master
branch
from
2029080 to
0fd8306
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Suggestion for fixing the error "SQL error code = -204
Implementation limit exceeded
block size exceeds implementation restriction" reported some time ago in an issue, I managed to find the point where I needed a test to know the field type and field size.
Test case, I have fields in the Firebird 2.5 database of type CHAR, when I connect via net 8.0 or higher, doing a Where with these fields, I noticed that the code always returned a Cast to Varchar(maxlength), this caused the exception.
Example: Where(p=> p.Field == "Value")