In debugging an issue on 5.10.1 I've found that the ad_set_client_property proc is not persisting the initial value to the database. Subsequent calls will update the value properly but the initial call does not set property_value column.
This is on PostgreSQL and the way the db function is written the update is not setting the value on the INSERT statement and the way the author expected the LOOP to work appears to be exiting early after the initial INSERT.
For now one way to resolve it in our testing is to just include the property_value in the INSERT so the value is initialized properly. The problematic db function is sec_session_property__upsert
Is there a reason why the `insert into sec_session_properties` call wouldn't have included the property_value column as part of the initial insert?
Thanks.
