You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
millerjp
changed the title
[bug]: Right Click - Remove table name can not be edited warning on alter table
[bug]: Right Click - Remove "table name can not be edited" warning on alter table
Jan 11, 2025
- Similar to #667 ticket, the altering warning for standard table's name has been removed.
- Also, it has been removed when altering counter tables and UDTs.
…#685, #684, #649, #596, #670, #577, #360, #522, and #682 (#726)
* For ticket #666, dynamic RF name based on strategy
When altering/creating a keyspace, the `Replication Factor` name would be changed to be `Data Center Replication Factor` in case the set strategy is `NetworkTopology`
* For ticket #591, added `Mandatory` badge to required fields on keyspace creation
- Now a badge `Mandatory` is showed for the `Keyspace Name` field; to tell that it's a required field to complete the creation process.
- Improved the style of other mandatory fields in connection addition process - host name and port -.
* For ticket #667, warning about keyspace name in alter process has been removed
The warning `The keyspace name can't be altered` has been removed; as the field is disabled already.
* For ticket #663, altering warning for name has been removed everywhere
- Similar to #667 ticket, the altering warning for standard table's name has been removed.
- Also, it has been removed when altering counter tables and UDTs.
* For ticket #685, improved the metadata treeview, changed icons for partition and clustering keys
The icon of both; partition and clustering keys have been changed in order to be clearly distinguished
* For ticket #684
* For ticket #649, and ticket #670 - handled in previous commits -
* For ticket #577
* For ticket #360
* For ticket #522
* For ticket #682
The form field is non-editable so no-need to display the warning
Similar to #667
The text was updated successfully, but these errors were encountered: