I have a dataset of German addresses, originally in utf8 and using German umlaut characters such as ÄÖÜäöüß, which I have imported both directly into the SQL database as well as through the App. In both cases the dat is shown correctly in MySQL, but not in the App.
If I import the data in Windows Latin 1, even though the database is set to utf8, it displays correctly in the app.
What to do? I have been through all charset instances in the generated files, all are set to outfit, as is the choice in the App itself.
As an aside, I don't understand why one cannot use umlaut characters in field names - SQL accepts than with no bother.
öüä correct in MySQL, shown incorrectly in App
Re: öüä correct in MySQL, shown incorrectly in App
Hmm ... If I understand correctly, "Latin1" displays the correct characters while utf-8 not. Right? It depends on how your source data was encoded, regardless of the database encoding. When AppGini connects to your database, it sets the connection encoding to that configured in AppGini.

- DataTalk is an innovative AppGini plugin based on ChatGPT that allows you to interact with your AppGini database using natural language questions, without writing any SQL. Check the demo video
- Check our other plugins and get a generous discount of up to 30% when buying 2 or more plugins.
- Need personalized consulting on your specific app and customizations? Book an online call with me here.