<![CDATA[LiveCloud Forums - Code Samples]]> https://forums.livecloud.io/ Fri, 08 May 2026 13:43:53 +0000 MyBB <![CDATA[Methods for integrating cdbUsers table with stored user content]]> https://forums.livecloud.io/showthread.php?tid=501 Wed, 27 Oct 2021 23:05:56 +0000 mark_talluto]]> https://forums.livecloud.io/showthread.php?tid=501 Once in a while, we will provide support via email. I want to share that experience with everyone with the hope that others will benefit. When this happens, We'll leave out the person's name.

On to the question:
I've never really done nosql, was always able to query specific records against a user_id.
I want a quick way to save and query all of a user's records in this nosql way.

Do you see any limits or problems with creating a table for each user? and place all their data there?

I know for low numbers of user's thats not a big deal.
How about 10,000 tables?


The response:
There is always more than one way to model your data.

Method 1
You could use your cdbRecordID (primary key) for each user in the cdbUsers table as a linking key (foreign key) to records in another table.

cdbUsers table
Record 1: [a2ad3bc9-8ef8-4c36-9c4d-00d109600cd9] [Marco] [Polo]


someDataTable that contains data for all of your users
Record 34545 [0a43839f-ad5c-4089-a864-c6bfa10942be] [a2ad3bc9-8ef8-4c36-9c4d-00d109600cd9] [import] [data] [in] [these] [columns]


TableID:fbb12a0d-8189-4fb4-a906-12166445f54b
0a43839f-ad5c-4089-a864-c6bfa10942be


//Untested come code that should work:
//GET THE RECORD ID OF A PARTICULAR USER
local tOutputA, tRecordID
put cdb_query("email","=","marco@polo.com","cdbUsers","cloud","recordData") into tOutputA
put tOutputA["cdb"]["cdbRecordID"] into tRecordID


//USE THE cdbRecordID FROM THE FIRST QUERY TO FIND ALL RELATED DATA TO THIS USER
local tOutputA
put cdb_query("userForeignKey","=",tRecordID,"someDataTable","cloud","recordData") into tOutputA

//tOutputA will contain an array that for every record in the 'someDataTable' table that is related to your user. 
//For this to work, every commit to this table needs you to include the foreign key value in each record for every user.
//Since the user is probably authenticated, you can get this value one time during their session and use it everywhere you need.


Method 2
You can store the tableID in the cdbUsers table as a foreign key.
The optimization is that you can read on a single table and know that all the data is related to that particular user. You will not need to query a table to find related data. 

I am in favor of this model. The only negative is that a user can not create a table programmatically. It is something we intend to resolve. You could pre-create tables with a developer-signed app programmatically. If you get serious with this method, we can look at a longer-term solution to make this happen. 

You can connect as many tables as you like to a particular user. Just create the foreign key columns in the cdbUsers table to track the tableIDs.


Limitations
The free account “Mist” and entry level account “Rain" are running on a shared cloud cluster. They are great for developing concepts and low-data consumption apps. They will not work out for you if you plan to have 10k or more users. 

You will want to build a “Storm” account to customize the cluster just for your app. If you have 10k paying customers, our Storm plans are cheap. ]]> Once in a while, we will provide support via email. I want to share that experience with everyone with the hope that others will benefit. When this happens, We'll leave out the person's name.

On to the question:
I've never really done nosql, was always able to query specific records against a user_id.
I want a quick way to save and query all of a user's records in this nosql way.

Do you see any limits or problems with creating a table for each user? and place all their data there?

I know for low numbers of user's thats not a big deal.
How about 10,000 tables?


The response:
There is always more than one way to model your data.

Method 1
You could use your cdbRecordID (primary key) for each user in the cdbUsers table as a linking key (foreign key) to records in another table.

cdbUsers table
Record 1: [a2ad3bc9-8ef8-4c36-9c4d-00d109600cd9] [Marco] [Polo]


someDataTable that contains data for all of your users
Record 34545 [0a43839f-ad5c-4089-a864-c6bfa10942be] [a2ad3bc9-8ef8-4c36-9c4d-00d109600cd9] [import] [data] [in] [these] [columns]


TableID:fbb12a0d-8189-4fb4-a906-12166445f54b
0a43839f-ad5c-4089-a864-c6bfa10942be


//Untested come code that should work:
//GET THE RECORD ID OF A PARTICULAR USER
local tOutputA, tRecordID
put cdb_query("email","=","marco@polo.com","cdbUsers","cloud","recordData") into tOutputA
put tOutputA["cdb"]["cdbRecordID"] into tRecordID


//USE THE cdbRecordID FROM THE FIRST QUERY TO FIND ALL RELATED DATA TO THIS USER
local tOutputA
put cdb_query("userForeignKey","=",tRecordID,"someDataTable","cloud","recordData") into tOutputA

//tOutputA will contain an array that for every record in the 'someDataTable' table that is related to your user. 
//For this to work, every commit to this table needs you to include the foreign key value in each record for every user.
//Since the user is probably authenticated, you can get this value one time during their session and use it everywhere you need.


Method 2
You can store the tableID in the cdbUsers table as a foreign key.
The optimization is that you can read on a single table and know that all the data is related to that particular user. You will not need to query a table to find related data. 

I am in favor of this model. The only negative is that a user can not create a table programmatically. It is something we intend to resolve. You could pre-create tables with a developer-signed app programmatically. If you get serious with this method, we can look at a longer-term solution to make this happen. 

You can connect as many tables as you like to a particular user. Just create the foreign key columns in the cdbUsers table to track the tableIDs.


Limitations
The free account “Mist” and entry level account “Rain" are running on a shared cloud cluster. They are great for developing concepts and low-data consumption apps. They will not work out for you if you plan to have 10k or more users. 

You will want to build a “Storm” account to customize the cluster just for your app. If you have 10k paying customers, our Storm plans are cheap. ]]> <![CDATA[cdb_update changed/new data - best practices]]> https://forums.livecloud.io/showthread.php?tid=437 Tue, 09 Jun 2020 19:55:02 +0000 mark_talluto]]> https://forums.livecloud.io/showthread.php?tid=437
Suppose the following array (record):

tInputA =
[“firstName”]
[“lastName”]
[“age”]
[“phone”]

Existing record id "435756d6-0576-4a86-8d01-7557168f6528" contains:

firstName: Tom
lastName: Perkins
age: 78
Phone: 123-456-7890

If you pass an array like: 
tInputA =
[“firstName”][“Tom”]
[“lastName”][“Perkins”]
[“age”][“78”]
[“phone”][“555-888-9999”]

This will push an update to all the keys in this array even though some of the data may not have changed.

If you pass an array like:
tInputA =
[“phone”][“555-888-9999”]

You are only touching the “phone” key. The other data will stay as it is. The cloud call will be smaller and more efficient (...marginally). The question is how do you know that the phone data has has been updated?

It sounds like you are looking to come up with a method to pass as little data as possible (optimization) by determining what has changed.
This can be an important optimization if your array contains many keys. Or, it you may have heavy data in some of the keys. LiveCloud is not able to determine what is new for you without making a round trip to the cloud and compare. Solving this in your app is best.

People solve this problem in different ways.

Method #1: Develop a flag system to track which fields have been touched by your app
Method #2: Use the set operations in LiveCode to compare the original array with the final version and see if changes have been made
Method #3: Send the full array up using cdb_update and let LiveCloud push both new and old data into place
Method #4: Pick up the changes in a field and call cdb_update as each field is updated with: closeField

I am going to supply you the code to do Method #2 as it is not always apparent how to do this. 
Drop this code into a single button. Put breakpoints into the code so you can walk through it. Once you get the hang of it, you can use this API in your own code.


—COPY ALL THE CODE BELOW TO A SINGLE BUTTON IN LIVECODE
//>GLOBALS
global gArrayA1, gArrayA2


on mouseUp
     local tInputA, tRecordID
     
     --BUILD THE TWO ARRAYS TO COMPARE
     buildArray1
     buildArray2
     
     --CALL CUSTOM API TO COMPARE THE TWO ARRAYS
     put compareTwoArrays(gArrayA1,gArrayA2) into tInputA
     
     --WE NEED TO CONVERT THIS ARRAY
     --THE KEY AND VALUE NEED TO BE IN THE RIGHT PLACE
     combine tInputA with lf and empty
     split tInputA with lf and comma

     --RECORD TO BE UPDATED
     put "435756d6-0576-4a86-8d01-7557168f6528" into tRecordID
     
     --DO CLOUD UPDATE
     cdb_update tInputA,"myTableName", tRecordID
end mouseUp


function compareTwoArrays pArray1, pArray2
     local tArrayA3
     
     /* BREAKPOINT THROUGH THIS TO SEE WHAT IS HAPPENING STEP BY STEP */
     
     --TURN ARRAYS INTO A STRING
     --WE ARE TAKING THE ELEMENT AND ITS VALUE AND SMASHING THEM TOGETHER
     --gArrayA1 WOULD BE YOUR CURRENT CLOUD OR LOCAL RECORD
     --gArrayA2 WOULD BE THE ARRAY CAPTURED FROM YOUR APP THAT MAY HAVE NEW OR UPDATED DATA
     combine pArray1 with lf and comma
     combine pArray2 with lf and comma
     
     --TURN STRING BACK INTO AN ARRAY
     --WE WANT THE COMBINED KEY AND VALUE TO BE THE NEW ELEMENT
     --THIS WILL MAKE IT EASY TO COMPARE THE TWO ARRAYS
     --IT IS INTENDED THAT THE VALUE WILL BE EMPTY
     split pArray1 with lf and empty
     split pArray2 with lf and empty
     
     --WE DO A SET OPERATION TO FIND WHICH DATA IS NEW
     --DIFFERENCE IS ONLY LOOKING AT THE ELEMENT, NOT THE VALUE OF THE KEY WHEN DOING ITS OPERATION
     --WHATEVER IS LEFT IN THE tArrayA3 ARRAY IS NEW
     difference pArray2 with pArray1 into tArrayA3
     
     return tArrayA3
end compareTwoArrays


on buildArray1
     /* CHANGE THIS ARRAY TO MATCH YOUR TABLE */
     put "Tom" into gArrayA1["firstName"]
     put "Perkins" into gArrayA1["lastName"]
     put "78" into gArrayA1["age"]
     put "123-456-7890" into gArrayA1["phone"]
end buildArray1


on buildArray2
     /* CHANGE THIS ARRAY TO MATCH YOUR TABLE */
     put "555-888-0000" into gArrayA2["phone"]
end buildArray2]]>
Suppose the following array (record):

tInputA =
[“firstName”]
[“lastName”]
[“age”]
[“phone”]

Existing record id "435756d6-0576-4a86-8d01-7557168f6528" contains:

firstName: Tom
lastName: Perkins
age: 78
Phone: 123-456-7890

If you pass an array like: 
tInputA =
[“firstName”][“Tom”]
[“lastName”][“Perkins”]
[“age”][“78”]
[“phone”][“555-888-9999”]

This will push an update to all the keys in this array even though some of the data may not have changed.

If you pass an array like:
tInputA =
[“phone”][“555-888-9999”]

You are only touching the “phone” key. The other data will stay as it is. The cloud call will be smaller and more efficient (...marginally). The question is how do you know that the phone data has has been updated?

It sounds like you are looking to come up with a method to pass as little data as possible (optimization) by determining what has changed.
This can be an important optimization if your array contains many keys. Or, it you may have heavy data in some of the keys. LiveCloud is not able to determine what is new for you without making a round trip to the cloud and compare. Solving this in your app is best.

People solve this problem in different ways.

Method #1: Develop a flag system to track which fields have been touched by your app
Method #2: Use the set operations in LiveCode to compare the original array with the final version and see if changes have been made
Method #3: Send the full array up using cdb_update and let LiveCloud push both new and old data into place
Method #4: Pick up the changes in a field and call cdb_update as each field is updated with: closeField

I am going to supply you the code to do Method #2 as it is not always apparent how to do this. 
Drop this code into a single button. Put breakpoints into the code so you can walk through it. Once you get the hang of it, you can use this API in your own code.


—COPY ALL THE CODE BELOW TO A SINGLE BUTTON IN LIVECODE
//>GLOBALS
global gArrayA1, gArrayA2


on mouseUp
     local tInputA, tRecordID
     
     --BUILD THE TWO ARRAYS TO COMPARE
     buildArray1
     buildArray2
     
     --CALL CUSTOM API TO COMPARE THE TWO ARRAYS
     put compareTwoArrays(gArrayA1,gArrayA2) into tInputA
     
     --WE NEED TO CONVERT THIS ARRAY
     --THE KEY AND VALUE NEED TO BE IN THE RIGHT PLACE
     combine tInputA with lf and empty
     split tInputA with lf and comma

     --RECORD TO BE UPDATED
     put "435756d6-0576-4a86-8d01-7557168f6528" into tRecordID
     
     --DO CLOUD UPDATE
     cdb_update tInputA,"myTableName", tRecordID
end mouseUp


function compareTwoArrays pArray1, pArray2
     local tArrayA3
     
     /* BREAKPOINT THROUGH THIS TO SEE WHAT IS HAPPENING STEP BY STEP */
     
     --TURN ARRAYS INTO A STRING
     --WE ARE TAKING THE ELEMENT AND ITS VALUE AND SMASHING THEM TOGETHER
     --gArrayA1 WOULD BE YOUR CURRENT CLOUD OR LOCAL RECORD
     --gArrayA2 WOULD BE THE ARRAY CAPTURED FROM YOUR APP THAT MAY HAVE NEW OR UPDATED DATA
     combine pArray1 with lf and comma
     combine pArray2 with lf and comma
     
     --TURN STRING BACK INTO AN ARRAY
     --WE WANT THE COMBINED KEY AND VALUE TO BE THE NEW ELEMENT
     --THIS WILL MAKE IT EASY TO COMPARE THE TWO ARRAYS
     --IT IS INTENDED THAT THE VALUE WILL BE EMPTY
     split pArray1 with lf and empty
     split pArray2 with lf and empty
     
     --WE DO A SET OPERATION TO FIND WHICH DATA IS NEW
     --DIFFERENCE IS ONLY LOOKING AT THE ELEMENT, NOT THE VALUE OF THE KEY WHEN DOING ITS OPERATION
     --WHATEVER IS LEFT IN THE tArrayA3 ARRAY IS NEW
     difference pArray2 with pArray1 into tArrayA3
     
     return tArrayA3
end compareTwoArrays


on buildArray1
     /* CHANGE THIS ARRAY TO MATCH YOUR TABLE */
     put "Tom" into gArrayA1["firstName"]
     put "Perkins" into gArrayA1["lastName"]
     put "78" into gArrayA1["age"]
     put "123-456-7890" into gArrayA1["phone"]
end buildArray1


on buildArray2
     /* CHANGE THIS ARRAY TO MATCH YOUR TABLE */
     put "555-888-0000" into gArrayA2["phone"]
end buildArray2]]> <![CDATA[Blobs and Datagrids]]> https://forums.livecloud.io/showthread.php?tid=407 Sun, 12 Apr 2020 12:52:40 +0000 sid]]> https://forums.livecloud.io/showthread.php?tid=407
I have a few questions on BLOBS and datagrids and will appreciate some sample code here.

I have managed to create a form with a datagrid on it , and a image object that retrieves the images from the cloud when a user hilites a line on the grid. This is designed as a cloudcall and not a local call , so its a tad slow.

here is a vid on how this works : https://www.loom.com/share/d609c74551df48309f51723192353039

here is the code:

Code:
local  tBlobGridRef, tPathToBlob, theLine, theSelectedID, tPHtender

getProp uSelectedPicID
 
  put the dgHilitedLines of me into theLine
  return GetDataOfLine(theLine,"blobReference")
 
end uSelectedPicID


on selectionChanged pHilitedIndex, pPrevHilitedIndex
 
  show widget "PHSpinner"
  put empty into tBlobGridRef
  put empty into tPathToBlob
 
  put the uSelectedPicID of group "Tenders" into theSelectedID
  put cdb_readBlob(theSelectedID,"cloud") into tPathToBlob
  set the filename of image "tenderPicViewer" to tPathToBlob
  //set the text of image "tenderPicViewer" to tPathToBlob
  put the text of image "PHTender" into tPHtender
  if tPathToBlob is empty then set the text of image "tenderPicViewer" to tPHtender
  hide widget "PHSpinner"
 
end selectionChanged
 

Here is  question 1. Its a cloud call but the path to the image ends up being a local path? Its pretty slow ,( perhaps because I'm living in a rural farm town) Does the system download the image if its a cloud based call or just look in the local Blobs table if it exists?

so I tried to resize all images to under 10kb and that helped a lot. Much faster, so I tried to put the text of the image into a table key, (not a BLOB table) figuring I can just store the text into the key and then that should speed it up more if its just a 100x80 pixel .png thumbnail. LCM did not seem to allow this? can we actually do that? Or will it totally mess up the performance?

Question 3 , Is it possible to put a thumbnail of a BLOB into a DataGrid? and if so, is it possible to only load the images that will be visible to the user (IE. only when the lines are visible on his screen. Will appreciate some help with this.
I am designing a system with at least 70000 product items and God help a tablet trying to load ...lets say 30000 thumbnails if a query is run. It will probably die...although it will be interesting to test. So the idea is run a LCM Query and put the results into a DataGrid table with a BLOB in one of the columns.

Question 4. Is it possible to have more than 1 Blobs table? because I feel that it important could separate things like documents and High Res images from thumbnails, because you do not want to sync the High Res Blob table with a thing like a POS system or a tablet.

Would really appreciate some sample code for question 3

I have to say that this is the easiest , most productive database design I have ever seen. I'm a total beginner and did not have to learn a single sql query with the code snippet feature . Thanks Livecloud !!!

Keep safe everyone!
Sid]]>
I have a few questions on BLOBS and datagrids and will appreciate some sample code here.

I have managed to create a form with a datagrid on it , and a image object that retrieves the images from the cloud when a user hilites a line on the grid. This is designed as a cloudcall and not a local call , so its a tad slow.

here is a vid on how this works : https://www.loom.com/share/d609c74551df48309f51723192353039

here is the code:

Code:
local  tBlobGridRef, tPathToBlob, theLine, theSelectedID, tPHtender

getProp uSelectedPicID
 
  put the dgHilitedLines of me into theLine
  return GetDataOfLine(theLine,"blobReference")
 
end uSelectedPicID


on selectionChanged pHilitedIndex, pPrevHilitedIndex
 
  show widget "PHSpinner"
  put empty into tBlobGridRef
  put empty into tPathToBlob
 
  put the uSelectedPicID of group "Tenders" into theSelectedID
  put cdb_readBlob(theSelectedID,"cloud") into tPathToBlob
  set the filename of image "tenderPicViewer" to tPathToBlob
  //set the text of image "tenderPicViewer" to tPathToBlob
  put the text of image "PHTender" into tPHtender
  if tPathToBlob is empty then set the text of image "tenderPicViewer" to tPHtender
  hide widget "PHSpinner"
 
end selectionChanged
 

Here is  question 1. Its a cloud call but the path to the image ends up being a local path? Its pretty slow ,( perhaps because I'm living in a rural farm town) Does the system download the image if its a cloud based call or just look in the local Blobs table if it exists?

so I tried to resize all images to under 10kb and that helped a lot. Much faster, so I tried to put the text of the image into a table key, (not a BLOB table) figuring I can just store the text into the key and then that should speed it up more if its just a 100x80 pixel .png thumbnail. LCM did not seem to allow this? can we actually do that? Or will it totally mess up the performance?

Question 3 , Is it possible to put a thumbnail of a BLOB into a DataGrid? and if so, is it possible to only load the images that will be visible to the user (IE. only when the lines are visible on his screen. Will appreciate some help with this.
I am designing a system with at least 70000 product items and God help a tablet trying to load ...lets say 30000 thumbnails if a query is run. It will probably die...although it will be interesting to test. So the idea is run a LCM Query and put the results into a DataGrid table with a BLOB in one of the columns.

Question 4. Is it possible to have more than 1 Blobs table? because I feel that it important could separate things like documents and High Res images from thumbnails, because you do not want to sync the High Res Blob table with a thing like a POS system or a tablet.

Would really appreciate some sample code for question 3

I have to say that this is the easiest , most productive database design I have ever seen. I'm a total beginner and did not have to learn a single sql query with the code snippet feature . Thanks Livecloud !!!

Keep safe everyone!
Sid]]> <![CDATA[Blob Viewer Stack to incorporate into projects]]> https://forums.livecloud.io/showthread.php?tid=399 Wed, 08 Apr 2020 16:19:44 +0000 sid]]> https://forums.livecloud.io/showthread.php?tid=399
I was wondering if its possible to release a BLOB viewer stack that people can use to incorporate into their projects?

Very similar to the login stack that you guys provide-, which makes it easy to get the basis of a projects started.

then all devs have to do is pass a BLOB id in the stack to and you have a Built in BLOB viewer from your own livecloud application.

you could also put it into the samples stack or the page that you use to export your toolkit. You can also add a button to replace the BLOB

that would be a great feature

Sid]]>
I was wondering if its possible to release a BLOB viewer stack that people can use to incorporate into their projects?

Very similar to the login stack that you guys provide-, which makes it easy to get the basis of a projects started.

then all devs have to do is pass a BLOB id in the stack to and you have a Built in BLOB viewer from your own livecloud application.

you could also put it into the samples stack or the page that you use to export your toolkit. You can also add a button to replace the BLOB

that would be a great feature

Sid]]> <![CDATA[Query cloud, modify a single key, update cloud]]> https://forums.livecloud.io/showthread.php?tid=391 Wed, 01 Apr 2020 17:49:33 +0000 mark_talluto]]> https://forums.livecloud.io/showthread.php?tid=391
Code:
on mouseUp
    local tInputA, tOutputA, tUpdatedLastName, tTableID
   
    put "Franklin" into tUpdatedLastName
    put cdb_tableID("Agents") into tTableID
   
    --QUERY FOR MATCHING DATA
    put cdb_query("lastName","=","Talluto","Agents","cloud","recordList") into tOutputA
   
    --REPEAT THROUGH EACH RECORD AND UPDATE THE 'lastName' VALUE FOR EACH RECORD FROM THE QUERY
    repeat for each line xRecordID in tOutputA
         put tUpdatedLastName into tInputA[tTableID][xRecordID]["lastName"]
    end repeat
   
    --UPDATE DATA IN THE CLOUD
    cdb_batchUpdate tInputA, "cloud"
end mouseUp
]]>
Code:
on mouseUp
    local tInputA, tOutputA, tUpdatedLastName, tTableID
   
    put "Franklin" into tUpdatedLastName
    put cdb_tableID("Agents") into tTableID
   
    --QUERY FOR MATCHING DATA
    put cdb_query("lastName","=","Talluto","Agents","cloud","recordList") into tOutputA
   
    --REPEAT THROUGH EACH RECORD AND UPDATE THE 'lastName' VALUE FOR EACH RECORD FROM THE QUERY
    repeat for each line xRecordID in tOutputA
         put tUpdatedLastName into tInputA[tTableID][xRecordID]["lastName"]
    end repeat
   
    --UPDATE DATA IN THE CLOUD
    cdb_batchUpdate tInputA, "cloud"
end mouseUp
]]> <![CDATA[Query Builder and Code Snippet]]> https://forums.livecloud.io/showthread.php?tid=366 Mon, 02 Mar 2020 21:08:22 +0000 efrain.c]]> https://forums.livecloud.io/showthread.php?tid=366
We've received a few questions regarding query. This video shows how you can use the query builder and code snippet to build a query and generate the code needed to perform the query: https://youtu.be/6g2pFEvdLcc

You can then take the code from the code snippet and use the output of the query to generate a list of names as follows:

Code:
local tInputA, tOutputA, tList

put cdb_query("trip","=","trip1","testTable","cloud","recordData") into tOutputA

//EACH KEY OF tOutputA CONTAINS THE recordID OF A RECORD THAT MATCHES THE QUERY CRITERIA
//WE REPEAT THROUGH EACH KEY TO ACCESS THE DATA IN EACH RECORD
repeat for each key xRecordID in tOutputA
    //GRAB THE NAME OF THE PERSON IN THIS RECORD TO CREATE A LIST
    put tOutputA[xRecordID]["person"] & lf after tList
end repeat

//DELETE TRAILING LF
delete char -1 of tList

We hope examples like this with short videos will be helpful. Let us know if there's a topic you would like us to cover.]]>
We've received a few questions regarding query. This video shows how you can use the query builder and code snippet to build a query and generate the code needed to perform the query: https://youtu.be/6g2pFEvdLcc

You can then take the code from the code snippet and use the output of the query to generate a list of names as follows:

Code:
local tInputA, tOutputA, tList

put cdb_query("trip","=","trip1","testTable","cloud","recordData") into tOutputA

//EACH KEY OF tOutputA CONTAINS THE recordID OF A RECORD THAT MATCHES THE QUERY CRITERIA
//WE REPEAT THROUGH EACH KEY TO ACCESS THE DATA IN EACH RECORD
repeat for each key xRecordID in tOutputA
    //GRAB THE NAME OF THE PERSON IN THIS RECORD TO CREATE A LIST
    put tOutputA[xRecordID]["person"] & lf after tList
end repeat

//DELETE TRAILING LF
delete char -1 of tList

We hope examples like this with short videos will be helpful. Let us know if there's a topic you would like us to cover.]]> <![CDATA[cdb_batchSync]]> https://forums.livecloud.io/showthread.php?tid=189 Fri, 11 Oct 2019 19:50:42 +0000 mark_talluto]]> https://forums.livecloud.io/showthread.php?tid=189
//THIS API WILL SYNC MULITPLE TABLES AT ONCE
//pInputA: This array contains primary keys of tableID. The secondary keys are
//(cdbRecordID,source,allowDeletes,detectCollisions)

—REPEAT THROUGH ALL TABLES AND BUILD AND INPUT ARRAY
—THIS EXAMPLE WILL DO FULL TABLE SYNCS
—YOU COULD SWITCH OUT THE ‘*’ FOR LINE DELIM RECORD IDS IF YOU WANT TO DO PARTIAL SYNCS
repeat for each line xTableID in cdb_tableID("*")
  put "*" into tInputA[xTableID]["cdbRecordID"]
  put “cloud" into tInputA[xTableID]["source"]
  put true into tInputA[xTableID]["allowDeletes"]
  put true into tInputA[xTableID]["detectCollisions"]
end repeat

put cdb_batchSync(tInputA) into tResults
if not cdb_result() then
  put "Error:" && cdb_result("response")
end if]]>
//THIS API WILL SYNC MULITPLE TABLES AT ONCE
//pInputA: This array contains primary keys of tableID. The secondary keys are
//(cdbRecordID,source,allowDeletes,detectCollisions)

—REPEAT THROUGH ALL TABLES AND BUILD AND INPUT ARRAY
—THIS EXAMPLE WILL DO FULL TABLE SYNCS
—YOU COULD SWITCH OUT THE ‘*’ FOR LINE DELIM RECORD IDS IF YOU WANT TO DO PARTIAL SYNCS
repeat for each line xTableID in cdb_tableID("*")
  put "*" into tInputA[xTableID]["cdbRecordID"]
  put “cloud" into tInputA[xTableID]["source"]
  put true into tInputA[xTableID]["allowDeletes"]
  put true into tInputA[xTableID]["detectCollisions"]
end repeat

put cdb_batchSync(tInputA) into tResults
if not cdb_result() then
  put "Error:" && cdb_result("response")
end if]]> <![CDATA[code to unpack query array to tab-delimited data?]]> https://forums.livecloud.io/showthread.php?tid=96 Mon, 19 Aug 2019 19:26:11 +0000 sltfn]]> https://forums.livecloud.io/showthread.php?tid=96
on mouseup
## query constructed above
 put cdb_batchQuery(tInputA,"cloud","logicalAND","recordData") into tOutputA
 put flattenArray( tOutputA) into flattened -- see flattenArray function below
end mouseup

function flattenArray A , d1, d2, T,  X
   if T is empty then
      if d1 is empty then put cr into d1
      if d2 is empty then put tab into d2
   end if
   if A is not an array then return T  & X & A & d1
   repeat for each key K in A
      put flattenArray( A[K],  d1, d2, T,  X & K & d2 )  into T
   end repeat
end flattenArray

This yields the queried records in this format (just one record of many shown here).

[CDB Table ID]    1    [CDB Record ID]    ATTRIBUTES    fopn
[CDB Table ID]    1    [CDB Record ID]    LAST_NAME    Jordan
[CDB Table ID]    1    [CDB Record ID]    STATUS    linnm
[CDB Table ID]    1    [CDB Record ID]    RANK    2
[CDB Table ID]    1    [CDB Record ID]    CITY    San Francisco
[CDB Table ID]    1    [CDB Record ID]    YEAR    2019
[CDB Table ID]    1    [CDB Record ID]    ROLE    5
[CDB Table ID]    1    [CDB Record ID]    NAME    Sam Jordan
[CDB Table ID]    1    [CDB Record ID]    DATE    2019-02-17
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbDateModified    1562677087
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbDateCreated    1562677087
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbRecordID    [CDB Record ID]
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbTableID    [CDB Table ID]
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbRecordVersion    1
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbTableName    stats
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbCloudSyncVersion    1

I then loop through the lines and remove the first two columns, then I filter out the lines with "cdb" keys not needed in my app as long as I preserve the record ID, and get a list of records like this…

[CDB Record ID]    ATTRIBUTES    fopn
[CDB Record ID]    LAST_NAME    Jordan
[CDB Record ID]    STATUS    linnm
[CDB Record ID]    RANK    2
[CDB Record ID]    CITY    San Francisco
[CDB Record ID]    YEAR    2019
[CDB Record ID]    ROLE    5
[CDB Record ID]    NAME    Sam Jordan
[CDB Record ID]    DATE    2019-02-17

Finally, I loop through the lines again and put the data for each record into the tab-delimited format I need, which is something roughly like this…

fopn    Jordan    linnm    2    San Francisco    2019    Sam Jordan    2019-02-17    [CDB Record ID]
ucpn    Smith    linnm    1    Los Angeles    2019    Susan Smith    2019-06-23    [CDB Record ID]

efrain.c and mark_talluto's suggestions for batch record creation and updates were VERY helpful. Thank you.

Does anybody have a simpler solution for this problem? Pretty sure there must be one (many). Thanks in advance.]]>
on mouseup
## query constructed above
 put cdb_batchQuery(tInputA,"cloud","logicalAND","recordData") into tOutputA
 put flattenArray( tOutputA) into flattened -- see flattenArray function below
end mouseup

function flattenArray A , d1, d2, T,  X
   if T is empty then
      if d1 is empty then put cr into d1
      if d2 is empty then put tab into d2
   end if
   if A is not an array then return T  & X & A & d1
   repeat for each key K in A
      put flattenArray( A[K],  d1, d2, T,  X & K & d2 )  into T
   end repeat
end flattenArray

This yields the queried records in this format (just one record of many shown here).

[CDB Table ID]    1    [CDB Record ID]    ATTRIBUTES    fopn
[CDB Table ID]    1    [CDB Record ID]    LAST_NAME    Jordan
[CDB Table ID]    1    [CDB Record ID]    STATUS    linnm
[CDB Table ID]    1    [CDB Record ID]    RANK    2
[CDB Table ID]    1    [CDB Record ID]    CITY    San Francisco
[CDB Table ID]    1    [CDB Record ID]    YEAR    2019
[CDB Table ID]    1    [CDB Record ID]    ROLE    5
[CDB Table ID]    1    [CDB Record ID]    NAME    Sam Jordan
[CDB Table ID]    1    [CDB Record ID]    DATE    2019-02-17
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbDateModified    1562677087
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbDateCreated    1562677087
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbRecordID    [CDB Record ID]
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbTableID    [CDB Table ID]
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbRecordVersion    1
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbTableName    stats
[CDB Table ID]    1    [CDB Record ID]    cdb    cdbCloudSyncVersion    1

I then loop through the lines and remove the first two columns, then I filter out the lines with "cdb" keys not needed in my app as long as I preserve the record ID, and get a list of records like this…

[CDB Record ID]    ATTRIBUTES    fopn
[CDB Record ID]    LAST_NAME    Jordan
[CDB Record ID]    STATUS    linnm
[CDB Record ID]    RANK    2
[CDB Record ID]    CITY    San Francisco
[CDB Record ID]    YEAR    2019
[CDB Record ID]    ROLE    5
[CDB Record ID]    NAME    Sam Jordan
[CDB Record ID]    DATE    2019-02-17

Finally, I loop through the lines again and put the data for each record into the tab-delimited format I need, which is something roughly like this…

fopn    Jordan    linnm    2    San Francisco    2019    Sam Jordan    2019-02-17    [CDB Record ID]
ucpn    Smith    linnm    1    Los Angeles    2019    Susan Smith    2019-06-23    [CDB Record ID]

efrain.c and mark_talluto's suggestions for batch record creation and updates were VERY helpful. Thank you.

Does anybody have a simpler solution for this problem? Pretty sure there must be one (many). Thanks in advance.]]> <![CDATA[The Code Sample Thread]]> https://forums.livecloud.io/showthread.php?tid=61 Fri, 26 Jul 2019 03:35:15 +0000 clarencemartin]]> https://forums.livecloud.io/showthread.php?tid=61 I will be posting things that I find and hope to get clarification of the LCM API's.]]> I will be posting things that I find and hope to get clarification of the LCM API's.]]>