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
Deviating fields are not being fixed
-
- Veteran Member
- Posts: 104
- Joined: 2018-12-10 21:52
-
- Veteran Member
- Posts: 104
- Joined: 2018-12-10 21:52
Re: Deviating fields are not being fixed
I have mixed up my mind... I answered myself another problem (err 500) solved recompiling... the main issue of deviating fileds still there..
Aldo
Aldo
Last edited by arcanebits on 2021-11-29 17:05, edited 1 time in total.
Re: Deviating fields are not being fixed
Did you skip
setup.md5
when uploading to your remote server?Kind regards,
<js />
My AppGini Blog:
https://appgini.bizzworxx.de/blog
You can help us helping you:
Please always put code fragments inside
AppGini 24.10 Revision 1579 + all AppGini Helper tools
<js />
My AppGini Blog:
https://appgini.bizzworxx.de/blog
You can help us helping you:
Please always put code fragments inside
[code]...[/code]
blocks for better readabilityAppGini 24.10 Revision 1579 + all AppGini Helper tools
Re: Deviating fields are not being fixed
Ok, that was simultaneously
Kind regards,
<js />
My AppGini Blog:
https://appgini.bizzworxx.de/blog
You can help us helping you:
Please always put code fragments inside
AppGini 24.10 Revision 1579 + all AppGini Helper tools
<js />
My AppGini Blog:
https://appgini.bizzworxx.de/blog
You can help us helping you:
Please always put code fragments inside
[code]...[/code]
blocks for better readabilityAppGini 24.10 Revision 1579 + all AppGini Helper tools
-
- Veteran Member
- Posts: 104
- Joined: 2018-12-10 21:52
Re: Deviating fields are not being fixed
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.
do you already have data in the modified field? If you have data that will not fit your new definition, the update will fail.
Any help offered comes with the best of intentions. Use it at your own risk. In any case, please make a backup of your existing environment before applying any changes.
-
- Veteran Member
- Posts: 104
- Joined: 2018-12-10 21:52
Re: Deviating fields are not being fixed
Ohhh! im quite sure you hit the problem, Let me go and Check!
Aldo
Aldo
-
- Veteran Member
- Posts: 104
- Joined: 2018-12-10 21:52
Re: Deviating fields are not being fixed
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
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
-
- Veteran Member
- Posts: 104
- Joined: 2018-12-10 21:52
Re: Deviating fields are not being fixed
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
Aldo
-
- Veteran Member
- Posts: 104
- Joined: 2018-12-10 21:52
Re: Deviating fields are not being fixed
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
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
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.FLOAT(5,3) NULL DEFAULT '.499' --->Appgini application
FLOAT(5,3) default '0.499' --->MariaDB
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.
AppGini plugins to add more power to your apps:
- 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
- Mass Update plugin: Update multiple records at once and improve your workflow efficiency.
- Check our other plugins and get a generous discount of up to 30% when buying 2 or more plugins.
-
- Veteran Member
- Posts: 104
- Joined: 2018-12-10 21:52
Re: Deviating fields are not being fixed
Ohhh ! on to it!