Property - Update
Update a Google Drive file property using SQL Server
- See SQLHTTP easy setup for Google Drive
- See API Call documentation for parameter values and other information
- Create the stored procedure documented below
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 |
CREATE PROCEDURE usp_Google_Property_Update( @Profile nvarchar(100), @fileId varchar(MAX), @propertyKey varchar(100), @visibility varchar(50) = NULL, @Body varchar(MAX), @Response nvarchar(MAX) OUTPUT, @StatusCode int OUTPUT, @StatusDescription nvarchar(MAX) OUTPUT) AS DECLARE @URL nvarchar(MAX) DECLARE @QueryString nvarchar(MAX) DECLARE @HTTPSessionID uniqueidentifier SET @URL = 'https://www.googleapis.com/drive/v2' EXEC SQLHTTP.net.UrlBuilder @URL OUTPUT, @Profile, 'files', @fileId, 'properties', @propertyKey EXEC SQLHTTP.net.QueryStringBuilder @QueryString OUTPUT, @Profile, 'visibility', @visibility SET @URL = @URL + @QueryString EXEC SQLHTTP.net.HTTPSession @HTTPSessionID OUTPUT EXEC usp_Google_Auth_Header @Profile, @HTTPSessionID EXEC SQLHTTP.net.HTTPRequest @HttpSessionID, @URL = @URL, @Method = 'PUT', @Body = @Body, @ContentType = 'application/json', @StatusCode = @StatusCode OUTPUT, @StatusDescription = @StatusDescription OUTPUT, @Response = @Response OUTPUT GO |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 |
DECLARE @Response nvarchar(MAX) DECLARE @StatusCode int DECLARE @StatusDescription nvarchar(MAX) DECLARE @Body varchar(MAX) DECLARE @Profile nvarchar(100) SET @Profile = 'My google' SET @Body = '{ "key": "Id", "value": "1569" }' --Google API Bearer Token expires after an hour EXEC usp_Google_Auth_Refresh @Profile EXEC usp_Google_Property_Update @Profile = @Profile, @fileId = '1IYC6qAejm7mJy4SKNx1LdkrOzINJ16iG', @propertyKey = 'Id', @visibility = 'PRIVATE', @Body = @Body, @Response = @Response OUTPUT, @StatusCode = @StatusCode OUTPUT, @StatusDescription = @StatusDescription OUTPUT IF @StatusCode >= 400 EXEC SQLHTTP.net.RaiseHttpError @StatusCode, @StatusDescription, @Response ELSE BEGIN DECLARE @X xml SET @X = SQLHTTP.net.Json_To_Xml(@Response, '0') --The XPath syntax below was easily generated by executing the following commands: --EXEC SQLHTTP.net.XQueryHelper @X --and then executing: --EXEC SQLHTTP.net.XQueryHelper @X, 'JsonObject' -- SELECT T.C.value(N'@kind', N'nvarchar(MAX)') AS [kind] ,T.C.value(N'@key', N'nvarchar(MAX)') AS [key] ,T.C.value(N'@value', N'nvarchar(MAX)') AS [value] ,T.C.value(N'@visibility', N'nvarchar(MAX)') AS [visibility] ,T.C.value(N'@selfLink', N'nvarchar(MAX)') AS [selfLink] FROM @X.nodes(N'/JsonObject') T(C) END |
|
1 2 3 4 5 |
kind key value visibility selfLink --------------- ------ ------- ----------- -------------------------------------------------- drive#property Id 1569 PRIVATE https://www.googleapis.com/drive/v2/files/1IYC6... |
- About – Fetch
- App – Fetch
- Apps – Fetch
- Change – Fetch
- Changes – Fetch
- Child File – Create
- Child File – Fetch
- Child File – Remove
- Children Files – Fetch
- Comment – Create
- Comment – Delete
- Comment – Fetch
- Comment – Update
- Comments – Fetch
- File – Copy
- File – Delete
- File – Fetch
- File – Patch
- File – Touch
- File – Trash
- File – Untrash
- Files – Fetch
- Parent Folder – Create
- Parent Folder – Fetch
- Parent Folder – Remove
- Parent Folders – Fetch
- Permission – Create
- Permission – Delete
- Permission – Fetch
- Permission – Patch
- Permission – Update
- Permission ID – Fetch
- Permissions – Fetch
- Properties – Fetch
- Property – Create
- Property – Delete
- Property – Fetch
- Property – Update
- Replies – Fetch
- Reply – Create
- Reply – Delete
- Reply – Fetch
- Reply – Update
- Revision – Delete
- Revision – Fetch
- Revision – Update
- Revisions – Fetch
- Start Page Token – Fetch
- Trashed Files – Delete
IMPORTANT DISCLAIMER
CODE/SQL ON THESE PAGES ARE PROVIDED AS-IS AND ARE AVAILABLE FOR ILLUSTRATIVE PURPOSES ONLY.
USERS ARE REQUIRED TO ABIDE BY THE TERMS AND CONDITIONS FOR USING REFERENCED THIRD PARTY WEBSITES AND/OR APIs FROM THEIR RESPECTIVE WEBSITES. WE DO NOT CONDONE ANY VIOLATION OF THIRD PARTY WEBSITES AND/OR APIs TERMS AND CONDITIONS USING OUR SOFTWARE.
USERS SHALL BE SOLELY RESPONSIBLE AND BE SOLELY LIABLE FOR VIOLATION OF ANY RULES SPECIFIED BY THIRD PARTIES FOR USING THEIR WEBSITES AND/OR APIs, OR INFRINGEMENT OF RIGHTS OF SUCH THIRD PARTIES.