Open SahilTikale opened 6 years ago
For the first two points, what's wrong with pg_dump/other standard database backup tools?
Re: the last point, I haven't found myself really wanting to hang on to SQLite databases for dev purposes. I'm dubious of a dev workflow that relies too much on state that isn't created programmatically. But if you really want to do this, you can also set up postgres locally...
I can see some utility in this, but it strikes me as not a good maintenence cost/complexity to payoff ratio.
I just wanted to know if we still need a show command and what exactly are we trying to display. I could take it up if needed.
I don't think anything has changed that would affect my thoughts on the matter above. Open to discussion, but for the sake of not leaving stale bugs open forever, I think if nobody makes a case for doing something here in a week or so I'll just close this.
I think if nobody makes a case for doing something here in a week or so I'll just close this.
Works for me.
@SahilTikale tagging you here so that you know.
Need a call that can dump all info stored in HIL DB as a json file that can be used as input to re-populate database.
Very useful for -- Creating point in time state of HIL db for research, debugging, backup -- Can be used for auditing (time series changes in HIL db) -- For developers (cloud computing students) that use sqlite3 there is no way to upgrade database in case of code changes, they have to re populate the database. This call can ease their life.