LiveCode Forums.

I have just watched the presentation about LiveCloud an wonder if anyone tell me how I might use Livecloud instead of an SQL database. What I don't understand is how the CassiaDb stores/edits duplicated data, for instance if I wanted to create an address book database in SQL I would probably create an address table and a person table. Each person record would point to an address record allowing the single address instance to be shared between a number of people records. If I understand correctly CassiaDb uses a single table meaning that in the example above the address data would be duplicated for each person at the address. Does that mean that the client application has to be responsible for ensuring that all copies of the address data are updated should an update be required?

CassiaDB can address multiple tables in the same way that SQL does. I would model my data the same way you have in your SQL example. I would use a 'linking key' (probably the recordID of the related record from the addressTable. I would then store that recordID with the appropriate people in the personTable. This creates normalized data.

You could on the other-hand store everything in a single table and manage the updating of records to keep them all in sync. We have a feature that has not been released yet that will do the work for you when storing all your data in a single table.

To learn more about LiveCloud, please check out our site at: livecloud.io.
There is a lot of sample code and actual apps you can download. We are about to release the LiveEvent App we made for the conference very soon. This will be another good example of multi-table database design that was made for mobile devices.

I hope this helps.

Hi Mark,

Thanks for your prompt response and answer to my questions. I will certainly have a look at your web site as I would like to understand how a no-sql database works.

Hi Simon,

Richard Gaskin has been working on me to use the term non-SQL instead of noSQL. Less of a confrontational label for sure. The other reality is that most noSQL databases do not support defined schemas. CassiaDB actually requires a defined schema for each table. If we made a chart of differences and similarities to various databases, I think we would find that CassiaDB actually falls right in the middle.

Hi,

Non-SQL it is then (but I'm not sure how to edit the title of this thread). I tried your web site but it would not open so I'll ask here, is CassiaDb able to run on a standalone isolated machine? By isolated I mean not connected to the internet.

best wishes

Simon

No worries on the title. Just a fun little tidbit. We still reference noSQL on our site. Did you try: http://livecloud.io
I just visited the site without issue. There is too much there to miss out on if you want to learn more. Let me know how it goes.

CassiaDB will run locally for sure. We have feature parity for both local databases and cloud databases. The best part is that the local database access is completely free with no limitations. Once you make your account (through the LiveCloud Manager App) you are free to get started.

The link to download LCM is: http://livecloud.io/download/

Richard Gaskin has been working on me to use the term non-SQL instead of noSQL.

I can understand that but I've always been under the impression that the "no" stood for "not only". not the word "no", implying that SQL isn;t the only database solution out there.
Pete

Hey Pete,

I did not realize that. I haven't been following the scene close enough lately.