Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save Demo Info #173

Open
tiimk opened this issue Jul 11, 2016 · 6 comments
Open

Save Demo Info #173

tiimk opened this issue Jul 11, 2016 · 6 comments

Comments

@tiimk
Copy link

tiimk commented Jul 11, 2016

I made another issue regarding this without any response. Not sure if was overlooked but just curious if there would be a way to save the stats from demos so that the demos may be removed.

@Rsslone
Copy link

Rsslone commented Jul 11, 2016

I don't think there is but I would be interested if this was a feature. Save and manage stats with a database.

@bugdone
Copy link
Owner

bugdone commented Jul 11, 2016

The problem is I keep changing the format of the stats as the code evolves. And keeping backwards compatibility with the old stats formats means more work.
Also new features won't work with the deleted demos since parsing is usually needed. Same for bugfixes.

@Rsslone
Copy link

Rsslone commented Jul 11, 2016

I see. Well its not a huge problem for me yet but I can imagine a day when the demo folder gets so large I have to start deleting them, which will be sad.

@0BuRner
Copy link

0BuRner commented Jul 11, 2016

As HSBox is using a sqlite database, maybe you could save a copy of the file before upgrading to a newer version. Will be unusable if DDL changes but at least you saved the data. The community could then create scripts to convert/dump it to newer version of the database.
You'll lost new data implemented in new version of the parser but it's better than nothing :)

@bugdone bugdone mentioned this issue Jul 11, 2016
@bugdone
Copy link
Owner

bugdone commented Jul 11, 2016

I must change the DDL myself whenever I change the format as re-parsing the demos is expensive.
But the code that works with the data is the problem.

In the end it might not be too much work since I didn't really changed the format much, I mostly added stuff.

@tiimk
Copy link
Author

tiimk commented Jul 11, 2016

I think it'd be really great because as Rsslone said storage isn't an issue yet but I plan on opening up my copy of hsb to my friends and between all of us we will be growing in size fairly fast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants