field default value in SQL
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: Tarantool
Since: 3.0
Root document: https://www.tarantool.io/en/doc/latest/reference/reference_sql/sql_statements_and_clauses/
SME: @ ImeevMA
Details
SQL now uses the default mechanism for BOX fields. The main difference
visible to the user is that now all NULL values explicitly inserted into
a field with a default value will be replaced with a default value,
which is different from the original SQL behavior. Additionally, default
values are now inserted instead of NULL after the SQL BEFORE INSERT
trigger but before the BOX BEFORE INSERT trigger. Previously,
SQL default values were inserted before the SQL BEFORE INSERT trigger.
Requested by @ImeevMA in https://github.com/tarantool/tarantool/commit/6cb86dc1738d40d5aba3f3001a1e01b3dae5cd16.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the SQL statements and clauses root document linked in the issue and compare its current description with the default-value behavior listed under Details. Document the NULL replacement and trigger-order differences, using commit 6cb86dc1738d40d5aba3f3001a1e01b3dae5cd16 as context; done means the SQL reference explains the Tarantool 3.0 behavior accurately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100