[MDEV-17450] Docs: clarify future behaviour of TRUNCATE for system-versioned tables Created: 2018-10-14 Updated: 2018-10-16 Resolved: 2018-10-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Documentation |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Federico Razzoli | Assignee: | Ian Gilfillan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | system_versioned_tables | ||
| Description |
|
Here: https://mariadb.com/kb/en/library/system-versioned-tables/ Doc says: "Currently, the TRUNCATE TABLE statement drops all historical records from a system-versioned-table." From this sentence, it is not clear if the future behaviour is going to change, if future behaviour is undecided, or if it has been decided but the sentence has not been updated. Please clarify, so users can confidently use TRUNCATE when appropriate. |
| Comments |
| Comment by Elena Stepanova [ 2018-10-14 ] |
|
I don't think the manual can and should make predictions about future behavior. |
| Comment by Federico Razzoli [ 2018-10-14 ] |
|
Then "currently" should be removed? As it is now, it sounds like a warning against possible future changes... |
| Comment by Ian Gilfillan [ 2018-10-16 ] |
|
I agree, have removed 'currently'. |