Page 1 of 1

Deviating fields are not being fixed

Posted: 2021-11-29 16:43
by arcanebits
Hi im runing on latest appgini 5.98 (1296), updated from previous version and tried to fix: Found 5 deviating fields that might need to be updated.
Sadly it does not fix it, it acts the same like trying but with no success.
Does anyonbe have found a workardound for this? or maybe I need to enter to the MariaDB and manualy fix?

Thank for any tip
Aldo

Re: Deviating fields are not being fixed

Posted: 2021-11-29 17:03
by arcanebits
I have mixed up my mind... I answered myself another problem (err 500) solved recompiling... the main issue of deviating fileds still there..

Aldo

Re: Deviating fields are not being fixed

Posted: 2021-11-29 17:04
by jsetzer
Did you skip setup.md5 when uploading to your remote server?

Re: Deviating fields are not being fixed

Posted: 2021-11-29 17:05
by jsetzer
Ok, that was simultaneously :lol:

Re: Deviating fields are not being fixed

Posted: 2021-11-29 17:07
by arcanebits
jsetzer wrote:
2021-11-29 17:04
Did you skip setup.md5 when uploading to your remote server?
I cant recall if I did. Is there a way to look into that?
Aldo

Re: Deviating fields are not being fixed

Posted: 2021-11-29 17:27
by pbottcher
Hi,

do you already have data in the modified field? If you have data that will not fit your new definition, the update will fail.

Re: Deviating fields are not being fixed

Posted: 2021-11-29 17:40
by arcanebits
Ohhh! im quite sure you hit the problem, Let me go and Check!
Aldo

Re: Deviating fields are not being fixed

Posted: 2021-11-29 18:16
by arcanebits
You where right, there where data living already in those fields, as the DB is Small and on development I manualy set data to zero so appgini work on it again into next edit.

The weird is this
FLOAT(5,3) NULL DEFAULT '.499' ----> Appgini
FLOAT(5,3) default '0.499' -----> MariaDB and still the deviant error

Im going to activate de NULL on the Maria and see how it goes.
Aldo

Re: Deviating fields are not being fixed

Posted: 2021-11-29 18:19
by arcanebits
Nothing, one (the easy waty out question) what will happen if I enter into de Maria and DELETE that field? AppGini will create it as if it where a first run?
Aldo

Re: Deviating fields are not being fixed

Posted: 2021-11-29 18:28
by arcanebits
Ok this is weird, and maybe its on my server side...
Heres what i did
1- Backup from appgini internal dump system
2- Deleted the Field
3- Amgini Noticed it, and said "you have a non existing table, we need to create it"
4- I said, sure go ahead, create it
5- It created but with the same issue
FLOAT(5,3) NULL DEFAULT '.499' --->Appgini application
FLOAT(5,3) default '0.499' --->MariaDB

This as far as I know is not breaking the WebApp, I just wanted to have no complains from Appgini in the admin panel.
I will dig it a little more, any tip is Welcome.
Aldo

Re: Deviating fields are not being fixed

Posted: 2021-12-23 12:15
by a.gneady
FLOAT(5,3) NULL DEFAULT '.499' --->Appgini application
FLOAT(5,3) default '0.499' --->MariaDB
Hmm ... I guess it's the default value that is confusing AppGini ... '.499' is the same as '0.499' but AppGini is making a string comparison rather than a numeric one, so they are not matching ... and when the app tries to change the default to '.499', it's seen by the db as '0.499', and so the deviation persists from the app's point of view.

I've taken note of that issue to add a fix to it in future releases. You might for now try setting the default value to '0.499' in the project file, regenerate, and see if that fixes the deviation.

Re: Deviating fields are not being fixed

Posted: 2022-01-10 17:08
by arcanebits
Ohhh ! on to it!