Tinyint fields converted to boolean

Wappler General Bugs
#1

MySQL8
macOS
3.8.3

All tinyint datebase fields are converted to boolean in the ui (and the action files too) and causing the server actions to be corrupted.

Boolean transforming to integers / number in Wappler and not refering to boolean type in wappler
Update fields in Database Mysql 8 and all boolean turned to tinyint and then Int
#2

I think this was added in the latest release.
Is this happening to tinyint(1) columns only or of any size?

#3

Don’t know, just seen it with tinyint so far.

#4

I expect it’s related to this thread and the change made as a result, as mentioned by @sid.

#5

I don’t understand this. Is that a bug or what else?

I just see that I have to check my whole work from the last weekend.

#6

I think what I reported was a bug, and I assumed it had been fixed. I’m still using v3.7.8 so haven’t checked this yet. I’ll probably upgrade soon.

(Edit: The issue I reported didn’t affect existing SC API files.)

#7

I consider this as a serious bug, as all new added filtered tinyint database fields are wongly implemented.

#8
#9

Thanks Teodor

#10

This should have been fixed in Wappler 3.8.3 update. Make sure to refresh the database table as it caches the field types.

#11

Hi Patrick, refresh where exactly? As refresh in insert/update panel still doesn’t work for me

#12

I see, reapply after refresh resets to number and “=”.

#13

The refresh only updates the metadata from the database, it does not update anything in the query, so you indeed have to reapply the condition after the refresh.

1 Like
Queries with boolean values not working
#14

Just to confirm: after upgrading to 3.8.3, is it necessary to make any changes - to reapply conditions using Tinyint - for existing API files to work, or is it only needed to update the UI so it displays correctly?

#15