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

Messages are lost when message type names or endpoint names contain Unicode chars #224

Closed
SzymonPobiega opened this issue Sep 26, 2016 · 4 comments
Milestone

Comments

@SzymonPobiega
Copy link
Member

SzymonPobiega commented Sep 26, 2016

Originally raised on GG https://groups.google.com/d/msgid/particularsoftware/3c156278-502a-4d22-a4b7-47533d75c64c%40googlegroups.com?utm_medium=email&utm_source=footer

Symptoms

A message is not published that should have been.

Who's affected

Users using Unicode characters in message types or endpoint names.

Root cause

Subscriber table uses VARCHAR in text columns.

@SimonCropp
Copy link
Contributor

@Particular/nhibernate-persistence-maintainers my understanding of this is equates to data loss. ie someone subscribes to an endpoint or a message type that contains a unicode character. when it is queried it will not match hence no publish will occur. or do i misunderstand the issue?

@SzymonPobiega
Copy link
Member Author

@SimonCropp Interesting problem. I'll validate the behavior because I am not sure at which stage the information gets lost.

@cremor
Copy link

cremor commented May 6, 2017

NServiceBus.Persistence.Sql uses NVARCHAR(200), so I assume that should work for NServiceBus.NHibernate too?

@WojcikMike WojcikMike changed the title Subscriber table uses VARCHAR instead of NVARCHAR in text columns Messages are lost when message type names or endpoint names contain Unicode chars Mar 29, 2021
@WojcikMike WojcikMike added this to the 8.4.4 milestone Mar 29, 2021
@WojcikMike
Copy link
Contributor

Released in version 8.4.4

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

5 participants