# How can i use Postgres or any other database for ignition config data? **URL:** \ **Category:** Ignition\ **Created:** [September 12, 2024, 12:44pm UTC](https://forum.inductiveautomation.com/t/how-can-i-use-postgres-or-any-other-database-for-ignition-config-data/95896 "2024-09-12T12:44:25Z")\ **Posts on this page:** 1\ **Showing post:** 14
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [September 12, 2024, 3:09pm UTC](https://forum.inductiveautomation.com/t/how-can-i-use-postgres-or-any-other-database-for-ignition-config-data/95896/14 "2024-09-12T15:09:24Z")
I know it's unlikely to change, but I'm tossing in another vote for something easier to diff than JSON. Over a year ago I added a json2yaml git textconv rule for all view.json files in my workspace, and it was the best damn thing I could've done. > [@Making it easier to diff Perspective view.json files](https://forum.inductiveautomation.com/t/making-it-easier-to-diff-perspective-view-json-files/58756): > > If you use git a lot and are frequently annoyed at trying to read diffs of scripts in Perspective view.json files, I’ve got something you might like. Git has a feature called [textconv](https://git.wiki.kernel.org/index.php/Textconv) which can be used to convert files to a text-friendly format before diffing them. It’s not expected to create a perfect or reversible text version, just something convenient for spotting changes. The perennial example is a PDF-to-txt converter, which would let you at least see text changes in PDF documents when yo… --- _[View the full topic](https://forum.inductiveautomation.com/t/how-can-i-use-postgres-or-any-other-database-for-ignition-config-data/95896)._