Hi,
I noticed that when I use repeat statements in my server action and insert records in a table within the repeat, an entry like the one below appears on its own.
This is the statement that generates the “record” entry under $_POST
Is this the behaviour to be expected in Wappler or am I doing something wrong within the repeat?
Many thanks!
Many thanks,
What’s your server action structure and what’s the issue exactly?
Have seen this many times. Its just that when we create a new INSERT server action step (or similar, don’t remember exactly) and save the step, the $_POST section in Globals add a “record” array with the variables of fields that were set in the insert step.
What I have found is that this is safe to delete… it does not really do anything. Its just additional JSON in the server action json file.
This is irrespective of the server model. Have seen this in both PHP & ASP.NET
Don’t have the exact steps to reproduce, but probably @aschoijett can provide.
I have seen the same also many times. Sometimes it’s useful, but usually it’s just unnecessary overhead.
This is very normal behaviour, and makes perfect sense, here is an example.
If you had a database table with 4 columns called
my_id, my_name, my_phone_number, my_date
In server connect you added a database connection step and a database single insert step after that, Wappler would auto generate $_POST variables for all columns that you have not manually set, as well as try determine which column is your ID and leave that one out.
Therefore the above example would make 3 $_POST variables for me, if I left their values in the insert step as Wapplers default
my_name, my_phone_number, my_date
The reason it does this is because a normal $_POST form would need to use the same variables in the names of their inputs, so when the Wappler Form generator gets hold of this it knows what to name your inputs.
Some things to be aware of however is lets say you did the insert as default and Wappler added the 3 variables as described, and then later on you decided to go and modify your insert step and make the my_date value a static value of {{NOW}}, Wappler is smart enough to know that value does not require a $_POST variable set firstly, but secondly because you already saved it previously, you still have a global $_POST variable of my_date just sitting there unused.
This is not exactly a problem, but if you are a pain like me and want it all neat and tidy, then what I do is when I have finalised my sever action, I normally go and delete all the $_POST variables under globals, and then click on all database insert or update steps, open them and just save them again, which regenerates only the $_POST variables I am really using in the server action. (Do this at your own risk). I am sometimes picky about which one I may leave alone, like a file upload variable etc.
If you use Multi Insert it will place the variables inside an array, with the name of the repeat step.
When doing a single database update step it generally makes all the same $_POST variables as an insert AND makes one extra $_POST variable for the condition which is for the ID of the database table by default.
A multi database update does the same as a single but again adds a repeat, and places all you $_POST variables inside an array with the same name as the repeat step.
The reason I am making a clarification of this is because if you just go remove all the auto generated global post variables then the auto form generator and the table generator are going to have a very hard time figuring out what to use as the input field name="" areas.
Hope this helps a little.
