Data manipulation language

It doesn't mean you can't do it.

You can still implement these unit tests to test every single DML operation that a Flow would test.

If we're testing these DML operations in Apex, why are we not testing them in Flows? Then you layer on top of

that.

I feel like you're speaking to so many people, though, because people have been asking for robust flow testing for so long.

Is there any other types of tests that you find are important now more so than ever? Aside from making sure and understanding that your flows and apexes are still working as they should, even pre-production or in production.

Any other testing that's important you've found over the last year or so?

So we covered the Apex test solution, but that only tests your DML operations for the most part.

And assume you have a lot more events and you're doing something.

Let's say you're doing a machine learning model or you're doing some DML and your code has changed now.

and your data looks a little different.

Or you'll be like, oh my God, I messed it up.

So if you want, I can go deep into it.

And basically it defines how the reads should be done or how the writes should be done.

And just a little bit of primer, copy on writes essentially means, let's say if you're doing any some DML operation, right? It will rewrite the new file.

So assume you have thousands of Parquet files in one Parquet file, which is 100 MB or 100 GB, you have 1 million records, right? but you only want to change one record, what it will do is it will rewrite the whole new file, right? It's great in terms of read because it'll be faster and referencing to the new file.

Yeah, I don't know, but I'd love to know.

DML.

Open your...

What are we asking for? Sleep