Is there a way to add a new Key in the Blob Table.

This could facilitate the identification of the image or pdf object saved in this file. At the moment the only info is the ID and the type of object.

My project will hold a number of image and pdf objects , for the moment the only solution I have is to create a separate table to  manage and identifty in a fast way the objects I save in the Blob table.

Is this the only solution ?

I need to add a new key to an existing table.

1 - I tried to use the Add Key button in the Manager. I am able to add the name of the key but cannot find the way to save this new key so I could enter data into it after. Is there a button or a procedure I can use ?

2 - I tried adding a key with the code I found in you documentation using this code:
command cdb_addKeys pTable, pKeys

on mouseUp pButtonNumber

local tTable, tKeys

put "Subject" into tTable

put "Why" into tKeys

cdb_addKeys tTable,tKeys
end mouseUp

 I get the following message in the message Windows:
(2019-06-10 20:50:24.543): Error: Failed API Key Authentication

So I checked for A way to log as Developper or Administrator, but I found code that uses "user" but does not tell me with what to replace "user" whit to identify myself as Administrator.
 

on preOpenStack

    initializeCanelaDB

    get cdb_auth(pEmail,pPassword,"user")
end preOpenStack

So What is the way to identify myself as Administrator so I can pass a command to add a new Key ?

Hello!

I'm getting error messages that seem strange. I started getting them in a stack I've been working on, but then I tried one of your sample stacks and got the same errors, so this bug report is for your sample stack "Contacts".

So, I created the project "Contacts" by using your sample project creator function in LCM. Out of the box, with no modifications at all, this is what I get in msg box when I open the stack:

These are the keys created when I have the LCM create a table in the cdbUser table:
firstName,lastName,email,password,projectID,teamID,appSignature,verified.
Can you provide the reason for the teamID and appSignature keys? Are you projecting any new keys for the future?
I'm sure they are for future use but what are the thoughts behind them and can you provide sample uses for them?

The new update for using 9.5 works well.
Thanks for the quick work.

If I continue developing with pre 9.4xx will I need to export to from the LCM for the fixes to work?

Is it possible to customize the verification email in any way? I mean the actual content of the email sent to new users?
Changing the logo and reply to-address would be great. 
Choice of language would be good too. 

Customizing the confirmation page after clicking the verification button/link in the email would also be great, although I understand that may be trickier to offer.
Currently the "BACK TO [project name]" button on the page links to livecloud.io. That seems odd to the user. Can at least that be changed somehow?

I read that backups are performed on the databases every 6 hours.
Can a particular backup be recovered through the LCM? Or is this a future feature?

The LCM's ability to do queries is great and presenting the code for such queries.
When will the LCM be capable of doing Multi-Table Queries and show the code for such queries?

The whole user account management and email verification feature is great and easy to set up and use. But what would be the best way here to create a lost password function, to allow the user to get a new password, without having to recreate the account?

If I am not mistaken I believe I saw a video somewhere demonstrating how CRUD code is generated in Livecloud. Would love to see it again. 
Learning by watching videos is a great way to get started. Would appreciate it if someone can point me to the URL.
The documentation is nicely structured and easy to follow.
In the past I have gone through numerous online manuals and it was extremely difficult to read as a result of the cluttered why it was presented.

Would like to see more tutorial / demonstration videos in future.
Good show guys.

Peter