Database Class and DML in a transaction

Question

According to the official document -

https://developer.salesforce.com/docs/atlas.en-us.198.0.apexcode.meta/apexcode/apex_transaction.htm

I understand that if there is any error in a transaction all the DML statement are rolled back and nothing is committed to the database. After reading this document:

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/langCon_apex_dml_database.htm

I read that if we give an additional parameter- false while calling a Database class to insert then we can do a partial commit to database and the record with error is rolled back.

So how does a Database.Insert operation with false attribute behaves in a transaction as compared to the DML operation - insert? Would the Database class allow a partial commit if there is any error in a transaction?

Answer 1

Yes database.insert allow the partial insert of records. eg you insert 500 records and and in 1 records you will get error then other records will be inserted successfully if you pass parameter false. if you set it to true then it will work as insert statement.

Second difference in insert statement if you get exception you need to handle that other wise you will get a message on UI but with Database.insert you can iterate over each records and get error message something like this

// DML statement
Database.SaveResult[] srList = Database.insert(acctList, false);

// Iterate through each returned result
for (Database.SaveResult sr : srList) {
    if (sr.isSuccess()) {
        // Operation was successful, so get the ID of the record that was processed
        System.debug('Successfully inserted account. Account ID: ' + sr.getId());
    }
    else {
        // Operation failed, so get all errors                
        for(Database.Error err : sr.getErrors()) {
            System.debug('The following error has occurred.');                    
            System.debug(err.getStatusCode() + ': ' + err.getMessage());
            System.debug('Account fields that affected this error: ' + err.getFields());
        }
    }
}

Other limits remain same for both. Normally when we want to create Dataloader type functionality we can use Database class