docs: EXPOSED-684 Add documentation for exec() and move transaction docs to new element #2385
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Summary of the change: Documentation about transactions now has its own top-level element with existing documentation as subtopics along with a new subtopic on working with SQL strings via
exec()
.Detailed description:
There have been issues/questions in the past about the proper way to use
exec()
and the only documentation mentioning it is currently in the FAQ page.There is a lot of information crammed into the single
Transactions.md
, which most likely deserves to be split and fleshed out into subtopics. Since the concept of a transaction is huge, and intertwines with other Exposed topics likeexec()
,Statements
, and interceptors, it most likely needs its own section.Transactions.md
file and place it under a new top-level element 'Transactions'StatementInterceptors
fromTransactions.md
to its ownmd
fileWorking-with-SQL-Strings.md
file that coversexec()
informationexposed-transactions
that currently only has new code examples for new topicType of Change
Please mark the relevant options with an "X":
Checklist
Related Issues
EXPOSED-684