The Database Insert Server Action is not returning anymore the ID of the inserted element although the output flag is selected and the entry is inserted correctly in the database.
This is what I receive when trying to debug:
and this is the Server Action:
Can you please confirm if this is a bug?
Wappler Version : 2.1.1
Operating System : Windows 10
Expected behavior
What do you think should happen?
The ServerAction should return the ID of the inserted element (ex: 91)
Actual behavior
What actually happens?
The serveraction returns null
How to reproduce
Create a database insert server action and check if an ID is returned when calling it from the frontend
Just to confirm @George, I am seeing this bug also, could have quite serious consequences for both new and existing sites which rely on the identity returned from an insert action
The identity variables is there maybe just not in the picker but you can still just enter it by hand like insert1.identity where insert1 is the name of your insert step.
I assume from that then that old sites will not break with the 2.1.1 update then if query.identity is used. To be honest I have locked the ftp on every site I do in fear of this breaking them
I see - we had indeed some changes made to improve the identity handling for PostgreSQL and that might have caused problems for the rest of the PHP drivers.
@patrick will check it out and will post a solution here, so you can just replace a single php file to have it working.