3 hours ago
Hi Stam,
Great questions.
We do this in one of our apps made in Appli. This app has themes. We use the blobs table and a themes table. First we create the blob in the blobs table. Next we take the blob cdbRecordID and use it as a linking key when we create the theme record in the themes table. The theme record has data about the theme including the name.
If you would like to avoid using another table with a linking key, you can add keys to the blobs table. After you create a blob, you can use cdb_update to populate the keys you added to the blobs table with more information about the blob. The same can be done with cdb_batchUpdate if you are batch uploading.
The upload should be blocking. Creating blobs will populate the output variable with the cdbRecordIDs of the new blobs after completion.
- Efrain
Great questions.
Quote:The question is: How am I meant to know which BLOB is which video? The only way I can see is to keep a separate database linking the cdbRecordID to a specific case, which introduces an unnecessary level of complexity.
We do this in one of our apps made in Appli. This app has themes. We use the blobs table and a themes table. First we create the blob in the blobs table. Next we take the blob cdbRecordID and use it as a linking key when we create the theme record in the themes table. The theme record has data about the theme including the name.
If you would like to avoid using another table with a linking key, you can add keys to the blobs table. After you create a blob, you can use cdb_update to populate the keys you added to the blobs table with more information about the blob. The same can be done with cdb_batchUpdate if you are batch uploading.
Quote:(as a sidenote, the upload seems to be deferred to the background as a non-blocking action, is there a callback option to notify completion?)
The upload should be blocking. Creating blobs will populate the output variable with the cdbRecordIDs of the new blobs after completion.
- Efrain