You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling a stored procedure with a named parameter that contains Umlauts,
these Umlauts get corrupted before the stored procedure is entered.
The same issue does not happen when the parameter is used to issue an update-statement.
This happened no matter what values where used for:
- Charset in the connection string
- Charset in the parameter
- FbDBType in the parameter
- DbType in the parameter
It seems as if the Charset gets ignored when calling a stored procedure that accepts a blob.
How the SP looks like? Why are you using NONE charset and why are you creating byte array from the string? The charset is handled by internals transparently, you don't have to create byte arrays or anything like that.
Submitted by: Ashwani Mehlem (amehlem)
When calling a stored procedure with a named parameter that contains Umlauts,
these Umlauts get corrupted before the stored procedure is entered.
The same issue does not happen when the parameter is used to issue an update-statement.
This happened no matter what values where used for:
- Charset in the connection string
- Charset in the parameter
- FbDBType in the parameter
- DbType in the parameter
It seems as if the Charset gets ignored when calling a stored procedure that accepts a blob.
Code that produced the error:
The text was updated successfully, but these errors were encountered: