Hi,
I have done this before in PHP, where emoji stored in DB tables with utf4mb4 collation get read and returned correctly by Wappler.
I now need to access a utf8mb4 table’s data in NodeJS app. I am able to store emojis in my text via insert without any issues. But when reading the same data, the response from server action is just full of ??. The data in table is correct and I can see emojis in my DB app.
Please help.
CC: @JonL
I have never used emojis but I’ll make a quick test.
Thanks. I found that manually adding charset to app/modules/connections/db.json does the trick.
But if you can find a better way, it would be great. This value keeps getting removed by Wappler on project change.
@JonL Any luck?
What db are you guys using?
MariaDB
No luck. Same issue.
Have you tried locking the permissions of the file to read only?
No, haven’t tried that. But it will mess with target switching. So no really a good way anyways.
The charset get removed, but it does not auto upload itself… So for remote targets, its not an issue.
Maybe @patrick can help out here.
Can you elaborate on that? I only use one target so I barely switch(just for DB manager).
Change the file in .wappler/targets/<target name>/database, that is the one that is copied over each time you change the target. It stores the database connections per target.
Perhaps @George can add the charset to the UI for the connection.
I think I did that. But on refresh of schema, it changes those back too.
Will recheck.
That would be best.
There is a project db file… and then there are target specific db files, which are stored in .Wappler folder (what Patrick has mentioned).
So on change of target, target specific db settings get over-written to the project db file.
Even if locked to read only? (the target file)
As Patrick says, it most likely does not even modify the target file.. so it is treated as read-only.
It reads and replaces contents on the project DB file.
I think I understand your point here though. Set charset and make the target specific file as read-only.
The problem again would be refreshing the schema. To do that I will have to unlock it, then refresh, then set charset and then finally lock it again.
If George could add charset in the DB connection settings, that would be best. 
This was added in Wappler 3.9.2
This topic was automatically closed after 29 hours. New replies are no longer allowed.