Second lookup for names in SQL
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Related dev. issue(s): https://github.com/tarantool/tarantool/issues/4467
Product: Tarantool
Since: 3.0
Root document: TBD check all SQL pages.
SME: @ ImeevMA
Details
Since all names are now case sensitive, a second lookup is now supported
to maintain backward compatibility. A second lookup by name will be
performed if the object was not found by name in the first lookup and if
the name is not enclosed in double quotation marks. The name for the
second lookup is normalized using old rules.
Requested by @ImeevMA in https://github.com/tarantool/tarantool/commit/a9d07e900beecf39d66e841260fe06ac54bc108c.
Definition of done
- SQL docs reflect the new lookup behavior
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
Start by reviewing the SQL documentation pages and the related development issue #4467 to identify where name lookup behavior is documented. Update the relevant SQL pages to describe the second lookup for unquoted names and the old-rule normalization; done means the SQL docs reflect this behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100