I think there should be consistency whenever possible - if a poorly-encoded string displays incorrectly (as it does on Desktop) that’s understandable.
But the OP is claiming that such a string causes the entire Web framework to stop working, which is much more severe issue and inconsistent with what we expect.
However, I’m not able to reproduce this behavior:
Sub Opening() Handles Opening
dim s as string = "🤢abcdéfg😁"
me.AddRow s
s = s.DefineEncoding(encodings.ISOLatin9)
me.AddRow s
s = s.DefineEncoding(nil)
me.AddRow s
s = s.ConvertEncoding(Encodings.UTF16BE)
me.AddRow s
s = s.DefineEncoding(nil)
me.AddRow s
End Sub
I think it raises a RuntimeException, which are handled poorly on Web. If you don’t implement a handler (whether that’s try...catch or the UnhandledException event), things just appear to silently fail.
If there is no RuntimeException, then I join you in being concerned.
DBngin makes it easy to set up databases, so I set up and ran your example project.
I was able to reproduce the issue. With 2024r4.2 it exhibits the telltale sign of a RuntimeException within the web framework (where it breaks into the debugger but there’s nothing visible).
Yes, there’s an example project on the issue ticket I linked that is self-contained. All I can say is that it failed in 2024r4.2 and that ticket is marked as fixed