You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
This is awesome and it helped me so much. Thank you for writing and making it available!
I wanted to share a couple of things, in case others encounter these struggles.
I was getting an error for sql queries because the 'sql' param was missing. I updated your query structure from: $service->query->sql($selectQuery);
to: $service->query->sql("sql"=>"$selectQuery");
Like @simonericciIssue while trying to insert a new row in FusionTable #2, I was getting forbidden errors when I tried to insert/delete rows. After setting up my Google service account, I grabbed the email address in the Service account ID column on this page. Then in my fusion table, I shared the table with this new email address, giving it editing privileges. Et voila! No more 403 forbidden errors.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is awesome and it helped me so much. Thank you for writing and making it available!
I wanted to share a couple of things, in case others encounter these struggles.
I was getting an error for sql queries because the 'sql' param was missing. I updated your query structure from:
$service->query->sql($selectQuery);
to:
$service->query->sql("sql"=>"$selectQuery");
Like @simonericci Issue while trying to insert a new row in FusionTable #2, I was getting forbidden errors when I tried to insert/delete rows. After setting up my Google service account, I grabbed the email address in the Service account ID column on this page. Then in my fusion table, I shared the table with this new email address, giving it editing privileges. Et voila! No more 403 forbidden errors.
The text was updated successfully, but these errors were encountered: