-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
PersistedExecutionPointer's EventName and EventKey are shorter than PersistedEvent's ones #898
Comments
@danielgerlag I'll prepare PR soon. But I'm stuck a bit with fixing it as we currently unable to migrate to .Net 5 (stuck on 4.6.2) so fixing EF5 migrations in WorkflowCore.Persistence.SqlServer does not seem as a fix for us. |
@danielgerlag please have a look #908 .
Maybe .csproj should reference the package with such name but appropriate version? |
Describe the bug
EventName and EventKey properties of PersistedExecutionPointer are attributed as MaxLength(100), same properties of PersistedEvent are attributed as MaxLength(200).
When WFC attempts to save event name and event key to ExecutionPointer in WaitFor() operation that are the same as in PublishEvent() and exceed 100 symbols execution fails with error 'SQL Server Error : String or binary data would be truncated'.
At that PublishEvent is successful.
Expected behavior
PublishEvent() and WaitFor() should behave consistently so MaxLength on both PersistedExecutionPointer and PersistedEvent should be aligned and be at least 200 (taking into account production data).
The text was updated successfully, but these errors were encountered: