Class BulkInsertPrepareValueMappingStep

java.lang.Object

com.kingsrook.qqq.backend.core.processes.implementations.bulk.insert.BulkInsertPrepareValueMappingStep

All Implemented Interfaces:

BackendStep

public class BulkInsertPrepareValueMappingStep
extends Object
implements BackendStep

Nested Class Summary

Nested Classes

Modifier and Type	Class	Description
static final record	BulkInsertPrepareValueMappingStep.TableAndField

Constructor Summary

Constructors

Constructor	Description
BulkInsertPrepareValueMappingStep()

Method Summary

Modifier and Type	Method	Description
static BulkInsertPrepareValueMappingStep.TableAndField	getTableAndField(String tableName, String fullFieldName)
void	run(RunBackendStepInput runBackendStepInput, RunBackendStepOutput runBackendStepOutput)	Execute the backend step - using the request as input, and the result as output.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

BulkInsertPrepareValueMappingStep

public BulkInsertPrepareValueMappingStep()

Method Details

run

public void run(RunBackendStepInput runBackendStepInput,
 RunBackendStepOutput runBackendStepOutput)
         throws QException

Description copied from interface: BackendStep

Execute the backend step - using the request as input, and the result as output. TODO - think about - why take the Result object as a param, instead of return it? Is this way easier for inter-language operability maybe? Also - there's way too much "process-specific gunk" in the Request object - can we simplify it?

Specified by:

run in interface BackendStep

Throws:

QException

getTableAndField

public static BulkInsertPrepareValueMappingStep.TableAndField getTableAndField(String tableName,
 String fullFieldName)
                                                                        throws QException

Throws:

QException