I’m not adding any geopoints. I’m merely updating a table that is related another table that contains a geopoint. (I’m not even touching the geopoint).
I have a PHP web service, it fetches a row from an Order table. Order table contains a related 1:1 customer (a User Class). A user class has a 1:M relation with a table called Address. And as you guessed, Address table has a geolocation column (1:1). All the relations have autoload on.
What happens is when I update the Order in the PHP web service, I get that 4002 error as mentioned in this post title. If I remove the geolocation from the related Address table, the update goes through just fine.
Why is that happening? Or what am I doing wrong?
note: even the geolocation column in the Address table has an autoload on. I need to have all the above relations mentioned with autoload on as my requirement.