Uses of Class
com.kingsrook.qqq.middleware.javalin.executors.io.TableInsertInput

Packages that use TableInsertInput

Package	Description
com.kingsrook.qqq.middleware.javalin.executors	This package contains (hopefully generally) api-version-agnostic classes that implement the actual QQQ Middleware.
com.kingsrook.qqq.middleware.javalin.executors.io	These classes are input/output wrappers for middleware executors.
com.kingsrook.qqq.middleware.javalin.specs.v1

Uses of TableInsertInput in com.kingsrook.qqq.middleware.javalin.executors

Subclasses with type arguments of type TableInsertInput in com.kingsrook.qqq.middleware.javalin.executors

Modifier and Type	Class	Description
class	TableInsertExecutor

Methods in com.kingsrook.qqq.middleware.javalin.executors with parameters of type TableInsertInput

Modifier and Type	Method	Description
void	TableInsertExecutor.execute(TableInsertInput input, TableInsertOutputInterface output)	Insert the record (with any associated records), checking the insert permission and the write permissions of every association, as the legacy insert route does.

Uses of TableInsertInput in com.kingsrook.qqq.middleware.javalin.executors.io

Methods in com.kingsrook.qqq.middleware.javalin.executors.io that return TableInsertInput

Modifier and Type	Method	Description
TableInsertInput	TableInsertInput.withRecord(QRecord record)	Fluent setter for record
TableInsertInput	TableInsertInput.withRecordValues(Map<String,Serializable> recordValues)	Fluent setter for recordValues
TableInsertInput	TableInsertInput.withTableName(String tableName)	Fluent setter for tableName

Uses of TableInsertInput in com.kingsrook.qqq.middleware.javalin.specs.v1

Subclasses with type arguments of type TableInsertInput in com.kingsrook.qqq.middleware.javalin.specs.v1

Modifier and Type	Class	Description
class	TableInsertSpecV1

Methods in com.kingsrook.qqq.middleware.javalin.specs.v1 that return TableInsertInput

Modifier and Type	Method	Description
TableInsertInput	TableInsertSpecV1.buildInput(io.javalin.http.Context context)	Read the record from a JSON object body, or from multipart form fields (uploaded files for blob fields, and an `associations` field), the same way the legacy insert route does - after the insert permission check, so a refused request is not read (an unknown table is refused the same way).