Tcl
Tcl
Firebase PUT - Writing Data
See more Firebase Examples
Demonstrates how to PUT new data to a Firebase JSON database. The data used in this example is at Chilkat Firebase Pigs Database, and is shown here:
Chilkat Tcl Downloads
load ./chilkat.dll
set success 0
# Demonstrates how to PUT new data to a Firebase JSON database.
# This example requires the Chilkat API to have been previously unlocked.
# See Global Unlock Sample for sample code.
# This example assumes a JWT authentication token, if required, has been previously obtained.
# See Get Firebase Access Token from JSON Service Account Private Key for sample code.
# Load the previously obtained Firebase access token into a string.
set fac [new_CkFileAccess]
set accessToken [CkFileAccess_readEntireTextFile $fac "qa_data/tokens/firebaseToken.txt" "utf-8"]
if {[CkFileAccess_get_LastMethodSuccess $fac] != 1} then {
puts [CkFileAccess_lastErrorText $fac]
delete_CkFileAccess $fac
exit
}
set rest [new_CkRest]
# Make the initial connection (without sending a request yet).
# Once connected, any number of requests may be sent. It is not necessary to explicitly
# call Connect before each request.
set success [CkRest_Connect $rest "chilkat.firebaseio.com" 443 1 1]
if {$success != 1} then {
puts [CkRest_lastErrorText $rest]
delete_CkFileAccess $fac
delete_CkRest $rest
exit
}
set authGoogle [new_CkAuthGoogle]
CkAuthGoogle_put_AccessToken $authGoogle $accessToken
CkRest_SetAuthGoogle $rest $authGoogle
# Chilkat's sample data (pig-rescue data) is publicly readable at: https://chilkat.firebaseio.com/.json
# This data is publicly readable, but not writable. You'll need to
# run against your own database..
# Generate a new push ID.
set prng [new_CkPrng]
set pushId [CkPrng_firebasePushId $prng]
# We're going to add a new pig with just the name.
set pigRecord [new_CkJsonObject]
CkJsonObject_AppendString $pigRecord "name" "William"
set path [new_CkStringBuilder]
CkStringBuilder_Append $path "/pig-rescue/animal/"
CkStringBuilder_Append $path $pushId
CkStringBuilder_Append $path ".json"
# The string content of the last arg passed is {"name":"William"}
set jsonResponse [CkRest_fullRequestString $rest "PUT" [CkStringBuilder_getAsString $path] [CkJsonObject_emit $pigRecord]]
if {[CkRest_get_LastMethodSuccess $rest] != 1} then {
# Something happened in the communications (either no request was sent, or no response was received.
# (The Chilkat REST API also has lower-level methods where an app can send the request in one call,
# and then receive the response in another call.)
puts [CkRest_lastErrorText $rest]
delete_CkFileAccess $fac
delete_CkRest $rest
delete_CkAuthGoogle $authGoogle
delete_CkPrng $prng
delete_CkJsonObject $pigRecord
delete_CkStringBuilder $path
exit
}
# Check the response status code. A 200 response status indicates success.
if {[CkRest_get_ResponseStatusCode $rest] != 200} then {
puts [CkRest_responseStatusText $rest]
puts "$jsonResponse"
puts "Failed."
delete_CkFileAccess $fac
delete_CkRest $rest
delete_CkAuthGoogle $authGoogle
delete_CkPrng $prng
delete_CkJsonObject $pigRecord
delete_CkStringBuilder $path
exit
}
puts "$jsonResponse"
puts "Success."
# Note: In many of the Chilkat examples, you may notice strange ways
# of doing something that should be simpler and shorter. For example,
# building the path (above) could've been written differently,
# with some simple string concatenation.
#
# The reason is that the Chilkat examples are written in a
# proprietary "example code" scripting language,
# and then automatically generated to each of the different programming
# languages you see on example-code.com. The code generation is
# limited in what it can do. For example, string concatentation
# is not yet a feature of the "example code" scripting language (as of May 2016),
# and therefore you won't see the use of a programming language's string
# concatentation operators in any example.
#
delete_CkFileAccess $fac
delete_CkRest $rest
delete_CkAuthGoogle $authGoogle
delete_CkPrng $prng
delete_CkJsonObject $pigRecord
delete_CkStringBuilder $path