# Docker 0.258.7: Field Updates Not Written; Zombie Views Appear **URL:** \ **Category:** Self-Host\ **Created:** [December 12, 2024, 5:15pm UTC](https://community.nocodb.com/t/docker-0-258-7-field-updates-not-written-zombie-views-appear/1534 "2024-12-12T17:15:49Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![HG2S](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.nocodb.com/hg2s/32/575_2.png) [@HG2S](https://community.nocodb.com/u/HG2S)\ **Post date:** [December 13, 2024, 4:26pm UTC](https://community.nocodb.com/t/docker-0-258-7-field-updates-not-written-zombie-views-appear/1534/6 "2024-12-13T16:26:06Z")
> [@Navi](#): > > My suspicion is you may be pointing your NC\_DB environment variable to a previously used database and probably you have ended up deleting the data associated with them in other schemas or your PG credentials do not have permissions to other schemas of NC\_DB. I’m sure you are quite right and I am grateful for your elaboration of the issue, but it begs the question, how does one go about resetting or changing this assignment? Except for NC\_DB, which I will attend to directly, I have not yet found mention of a declaration for the database stored elsewhere in, say, an .env file. Can you clarify the issue for me? A sample yml is posted [here](https://community.nocodb.com/t/docker-0-258-7-redux-still-no-love/1535/2). Are there obvious problems with it that would lead to this issue? -Thank you --- _[View the full topic](https://community.nocodb.com/t/docker-0-258-7-field-updates-not-written-zombie-views-appear/1534)._