Update docs for TABLE statement#2885
Conversation
|
✔️ e122c18 -> Azure artifacts URL |
| which specifies that the tables are to be used (1, default) or not used (0). | ||
|
|
||
| With usetable_suffix = 0, when the procedure is called it ignores the tables | ||
| With ``usetable_<suffix> = 0``, when the procedure is called it ignores the tables |
There was a problem hiding this comment.
| With ``usetable_<suffix> = 0``, when the procedure is called it ignores the tables | |
| With ``usetable_<suffix> == 0``, when the procedure is called it ignores the tables |
|
|
||
| With usetable_suffix = 1, when the procedure is called, the | ||
| arg value is used to assign values to the "variables" by looking them up | ||
| With ``usetable_<suffix> = 1``, when the procedure is called, the |
There was a problem hiding this comment.
| With ``usetable_<suffix> = 1``, when the procedure is called, the | |
| With ``usetable_<suffix> == 1``, when the procedure is called, the |
| is saved. If the tables are out of date (a "dependency" has a different | ||
| is saved. If the tables are out of date (any of the ``dependencies`` has a different | ||
| value from its value the last time the tables were constructed) or have never | ||
| been created, the tables are created. |
There was a problem hiding this comment.
Could be split into two sentences:
A table is considered out-of-date if any of the ``dependencies`` has changed its value since the last time the table was constructed. If the table is out-of-date or has never been constructed it's (re-)created.
Though it might not be helpful.
| time than an interpolated table lookup. | ||
|
|
||
| Also note that for any argument value outside of the interpolation range, | ||
| the returned value of a function with a TABLE will always be the value at |
There was a problem hiding this comment.
I think only if the table is used will it clamp.
|
|
||
| Also note that for any argument value outside of the interpolation range, | ||
| the returned value of a function with a TABLE will always be the value at | ||
| the boundary (value at ``lowest`` if argument value is smaller than ``lowest``, |
There was a problem hiding this comment.
| the boundary (value at ``lowest`` if argument value is smaller than ``lowest``, | |
| the boundary, i.e. the value at ``lowest`` if argument value is smaller than ``lowest``, or the |
A math formula might be more effective.
| Also note that for any argument value outside of the interpolation range, | ||
| the returned value of a function with a TABLE will always be the value at | ||
| the boundary (value at ``lowest`` if argument value is smaller than ``lowest``, | ||
| value at ``highest`` if argument value is larger than ``highest``). |
There was a problem hiding this comment.
| value at ``highest`` if argument value is larger than ``highest``). | |
| value at ``highest`` if argument value is larger than ``highest``. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2885 +/- ##
==========================================
+ Coverage 67.20% 67.21% +0.01%
==========================================
Files 563 569 +6
Lines 104254 104712 +458
==========================================
+ Hits 70059 70386 +327
- Misses 34195 34326 +131 ☔ View full report in Codecov by Sentry. |
This comment has been minimized.
This comment has been minimized.
|
✔️ 51707da -> Azure artifacts URL |
This comment has been minimized.
This comment has been minimized.
|
|
✔️ 58485cc -> Azure artifacts URL |
|
I see some old suggestions but also see that PR was updated and approved afterward. So I will merge this. |




Add more details about how to use the TABLE statement and how it works.