# Question on Nightly Changelog Comment **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [December 6, 2022, 1:46pm UTC](https://forum.inductiveautomation.com/t/question-on-nightly-changelog-comment/67283 "2022-12-06T13:46:10Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\ **Post date:** [December 6, 2022, 1:46pm UTC](https://forum.inductiveautomation.com/t/question-on-nightly-changelog-comment/67283/1 "2022-12-06T13:46:10Z")
I seen the following in the most recent nightly changelog: > **6429: Moving a Tag with History causes duplicate sqlth\_te records to get created** > Fixed moving tags with history creating duplicate sqlth\_te records. Can someone explain what exactly the bug did and what this fixes? Thanks, ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 6, 2022, 4:34pm UTC](https://forum.inductiveautomation.com/t/question-on-nightly-changelog-comment/67283/2 "2022-12-06T16:34:48Z")
The title is perhaps more exciting than the actual fix. From my read of the bug, it's basically that if you had a tag rapidly storing history, then renamed it (from history's perspective, retiring the old and creating a single new tag) you would instead end up with multiple "new" entries in sqlth\_te. This does _not_ do anything to make migrating history between tags easier, or automatically redirect old data, or anything like that. Just fixes an edge case. ---
**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\ **Post date:** [December 7, 2022, 1:52pm UTC](https://forum.inductiveautomation.com/t/question-on-nightly-changelog-comment/67283/3 "2022-12-07T13:52:12Z")
Oh. I'm super disappointed now. Thanks for the clarification ---
**Author:** ![Cory.grube](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cory.grube/32/20476_2.png) [@Cory.grube](https://forum.inductiveautomation.com/u/Cory.grube)\ **Post date:** [December 14, 2022, 10:02pm UTC](https://forum.inductiveautomation.com/t/question-on-nightly-changelog-comment/67283/4 "2022-12-14T22:02:15Z")
Are there any plans to make moving tags and retaining history easier/automatic? On the surface it seems pretty straightforward - just updating the path in sqlth\_te. Is the devil in the details though? ---
**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\ **Post date:** [December 15, 2022, 1:50pm UTC](https://forum.inductiveautomation.com/t/question-on-nightly-changelog-comment/67283/5 "2022-12-15T13:50:40Z")
Link to the Ideas post. Please upvote people! > **[keep tag history values linked when tags are moved | Voters | Inductive...](https://inductiveautomation.canny.io/ignition-features-and-ideas/p/keep-tag-history-values-linked-when-tags-are-moved)** ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 15, 2022, 4:09pm UTC](https://forum.inductiveautomation.com/t/question-on-nightly-changelog-comment/67283/6 "2022-12-15T16:09:40Z")
I'm not deeply involved in the tag system. I know this is an area where they're aware of how painful it is for folks. I'm not sure what technical complications there might be.