However, just like we need exceptionally talented programmers to solve super complicated problems that were previously unsolvable, we will also need exceptional genetic programmers to decipher the mysteries of human DNA. I understand that programming DNA is much more complex than writing computer code. Perhaps there are already scientists somewhere in the world working on this. While I'm not entirely sure if this tech is possible, I believe that it's an area of research worth exploring. Hydra is a small freshwater animal that's capable of regenerating its body parts, including its head, when they get cut or trimmed. With such technology, we could potentially regenerate our organs at a much faster pace, similar to how a Hydra regrows after being cut or trimmed. It's fascinating to think about whether we can program the human DNA instruction set to work with the Hydra instruction set through a genetic adapter. As someone who is optimistic about the potential of AI to transform industries and improve people's lives, I believe that it is up to all of us to educate ourselves about the benefits and limitations of this technology, and work towards building a future where humans and AI can work together effectively and harmoniously.Ī survey of over 17,000 people indicates only half of us are willing to trust AI at work As we continue to develop and refine AI systems, and as more people become familiar with the technology and its capabilities, we may see a shift in attitudes towards greater trust and acceptance. A 50-50 balance between humans and AI can create a symbiotic relationship where each can bring unique strengths to the table. While this may seem like a discouraging statistic, I see this as a valuable starting point for building trust between humans and AI. If you just need it for Regulatory Purpose, Own Backup or any backup solution serves the purpose.The article cites a survey of over 17,000 people which reveals that only half of us are currently willing to trust AI in the workplace. The purpose of Big Objects is to make Old Data available in SF to be accessed or used in SF as an when needed.ĭue to some regulatory rules this information should be kept somewhere for a long period of time. You have to look for a backup tool like OWNBackup, AWS S3 etc. There is Long text-area 131,072 characters where you can store Base64 string of file, but that will not allow you to store huge files. Yes you cant use joins but hey, you can do an extra query to serve your purpose.Īttachments are a binary, not flat table that can be stored in database(CLOB and BLOB data is not supported by Big Objects). Now you can get all children of a parent using the ParentId Index. In the child, the object creates a field ParentID(18 digits) text which is Required and Index as 1. If you can replicate the same behaviour via your data-model you can archive big objectsĬreate 2 Big Objects, Object Parent and Object Child for your master-detail relationship. What Exactly are Lookups and MasterDetail fields? They are just Candidate Key (Primary Key for some other table). ![]() So the question here would be - how could we archive such master-detail hierarchy of objects? Should we try to pack them into single big object with some sort of json serialiazation of child records and long text are fields to save this? Or is it better to create two separate big objects, but without configuring any relationships between them? And also how to archive attachments then, since big objects do not support them?Īny suggestions/ideas would be appreciated.Īrchive master-detail relationship Custom Objects To make it tougher, child records also have bunch of attachments, which also should be archived. And unfortunately system does not support BigObject-to-BigObject lookup relationship. But the challenge for us here is that we need to archive objects which are in master-detail relationship. There is no problem with moving old records of some specific custom object into corresponding Big Object. So we've decided to try to use Big Objects for archival purposes. from previous years, but at the same time we cannot just remove them - due to some regulatory rules this information should be kept somewhere for a long period of time. We are running into a problem when querying and reporting performance is degrading due to having huge number of records on org of some specific custom objects.īasically in our use case, we are not interested in old records, e.g.
0 Comments
Leave a Reply. |