We are all facing strange and challenging times. Just like you, we're concerned about the COVID-19 pandemic. We are here to support our customers and communities. Our work environment has changed a bit to secure the safety of our team members. We are working from home and using various technology tools to maintain a high level of productivity. Our phones are directed to our homes so you can still reach us. Please feel free to contact us via email or phone.  

We appreciate your continued support of our products and services. Your impressive work inspires us to be the best we can be. LiveCloud is one of those critical services that empower developers to make products and services to better support your customers. With more people working from home, cloud technologies are more important than ever.

Canela is maintaining the same level of diligence in keeping the LiveCloud service stable and reliable. We are improving the technology daily and pushing updates to you when they are ready. You and your customers can rely on us as your database and backend of choice.

COVID-19 is a world problem. In times like this, we can see humanity at its best. With everyone working through this together, we get a sense of world community. United, we are a force that will see this through.

######## VERSION 2.5.7 (2020/04/01)
News: IMPORTANT CHANGES! While not required, it is highly suggested that you export the Toolkit to take advantage of the changes mentioned in this update.
- - - - - - - - - -

Bugfix: cdb_auth will build a new hardwareID if the local file that holds this value is empty.
Bugfix: We changed internal use of codeUnits back to chars. CodeUnits may have negative effects that are not intended. Chars is still a valid command and more accurately reflects what we need.

Improved: cdb_importJSON has been improved to support importing data from older versions of LCM. Special formatting of JSON data must be observed. Please see the documentation for more information.
Improved: cdb_importJSON and cdb_importCSV will automatically build missing keys from your schema of imported data.
Improved: cdb_importJSON and cdb_importCSV will maintain cdbRecordIDs if they are present in the data being imported. This is helpful if you want to maintain database relationships. 
Improved: cdb_importJSON and cdb_importCSV will now get an SDK update automatically to ensure we have the last information on table keys for a given table.
Improved: cdb_addKeys, cdb_createTable, cdb_renameKey will not be as restrictive in its illegal char check. We will now allow colons in key names.
Improved: LCM is more efficient when importing CSV and JSON data by removing a final sync that is no longer needed.

As you can see, this update comes with some big improvements to JSON and CSV import. You no longer need to build your keys before importing data. The API will handled it all for you. Other useful tidbits are in there as well. The docs are going to need an update to match the changes. That will come soon.

Enjoy the update!

This code will demonstrate how to query cloud data for a specific key and value. It will then update that value for all the matching records and update the cloud.

Hi Guys

I am getting along well , but ran into a bit of a problem.

I have an exchange rate table and want to batch update all of the selected keys with a given value (its the same value )

so here is the code I used , 

First a query getting the records I need and placing all the record ID's into an array. (list Query)

The Message Box says the records don,t exist.....but they do, Am I missing a repeat string here?  or is this code completely wrong?

The aim is basically to mass edit a specific key in a selected number of records . (change all the values in the key to the one specified)

Every once in a while, we update our best practices document. Our current version is available from this link:

http://www.canelasoftware.com/pub/canela...ctices.pdf

The outline for the document is: 

- Programming Style
- 3rd Party Tools
- In-House Tools
- Download Links to Internal Tools

The main takeaway would be to use strict compilation mode and follow certain variable naming conventions.

If you are curious about the tools we use to manage our studio, we list the chief services we find to be invaluable.

If you have any questions about our choices, please feel free to respond here. If you have some you would like to add for everyone's benefit, please write about them here.

It's not a bug, but "Could not read from server cache" and reading / contacting instance directly seems to take longer time ... 

I know I've read something about the cache before... Anyway to reset that, or what do we do if we find that the cache can not be read?

Br /John

The function for getting a list of anything from recordIDs to any combination of keys in your table is: cdb_list()

After the rework on the API, we needed to come back an update the docs to explain how to use this API. 

https://docs.livecloud.io/List/

This API is unique in that it does not return an array. It is instead a very simple line delimited string. You might find this useful for getting all the recordIDs of a table. Or, you may store data that is used to build text in your UI. The output of this API could be directed to the text of the control without any cleaning. You may want to sort the data if that is important. 

It could also be used to count duplicate values. Build an array from the list and have an accurate count of how many of a given value are duplicates.

--GET LIST OF FIRST NAMES IN TABLE Customers
--ACCESS DATA IN THE CLOUD
--FROM THE KEY firstName
put cdb_list("Customers","cloud","firstName") into tOutput

--REPEAT THROUGH THE STRING AND COUNT EACH NAME
repeat for each line xLine in tOutput
     add 1 to tCounterA[xLine]
end repeat

The value of tCounterA might look something like this:

tCounterA["Joe"][3]
              ["Julie"][4]
              ["Rick"][8]

You can now import JSON files into your apps programmatically. More modern systems will support JSON export. This new API allows you to integrate with such systems and bring their data into your app.

You can find the doc here: https://docs.livecloud.io/ImportJSON/

You will need to export the toolKit to your project to gain access to this API.

Hi Everyone. When we receive security updates from our data center providers, in this case, Digital Ocean, we want to pass the information to you. If you have any questions, please let us know. The quick takeaway is that Digital Ocean is on top of the recent security threats to datacenters and that we all benefit from their diligent efforts.

We wanted to provide some detail around three new security vulnerabilities and how they could impact your Droplets. These include the Load Value Injection vulnerability, also referred to as LVI, TRRespass, a Rowhammer-type vulnerability, and Snoop-assisted L1 Data Sampling, a L1TF-type vulnerability.

• Load Value Injection. This vulnerability could allow data stored in an Intel SGX enclave to be leaked. Fortunately, DigitalOcean does not use SGX in our production environment. Our infrastructure is not affected, and there is no action required to protect your Droplets.
  
  
• TRRespass. This vulnerability could potentially allow attackers to gain privileged access to certain systems using DDR4 memory, though targeting a specific system is very difficult in cloud environments. We are currently working with our hardware manufacturers to evaluate the scope of this vulnerability in our infrastructure and will provide updates if any action is required on your end.
  
  
• Snoop-assisted L1 Data Sampling. This is similar to other L1TFvulnerabilities we’ve seen previously. The mitigations we already have in place sufficiently address this vulnerability, and no further action is required to protect your Droplets.
  

Hi Everyone. We made a quick video showing how to post a new message on its own thread in our forums.

https://youtu.be/CzlLa9-V3oY

You can also see the short but growing list of other videos.

https://livecloud.io/get-started/