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

Allow Database import from PipePipe #11960

Closed
6 tasks done
Profpatsch opened this issue Jan 26, 2025 · 1 comment
Closed
6 tasks done

Allow Database import from PipePipe #11960

Profpatsch opened this issue Jan 26, 2025 · 1 comment
Labels
database Issue and PRs related to database operations feature request Issue is related to a feature in the app wontfix This issue will not be fixed

Comments

@Profpatsch
Copy link
Contributor

Checklist

  • I made sure that there are no existing issues - open or closed - which I could contribute my information to.
  • I have read the FAQ and my problem isn't listed.
  • I'm aware that this is a request for NewPipe itself and that requests for adding a new service need to be made at NewPipeExtractor.
  • I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.

Feature description

Be able to import an export from the PipePipe fork without crashing the app (best effort import).

Why do you want this feature?

PipePipe i a fork of NewPipe, which many people use if they need some of its features or because they want to try it out

However, when people want to switch back to NewPipe (it was mentioned on chat that PipePipe tends to be more buggy in situations), they cannot import their database, NewPipe will crash after import.

Additional information

There is a python script which does the migration already, so implementing would be as simple as

  • detecting that the db is a PipePipe db
  • including these small database changes into the Importer

Furthermore, we should stabilize the import in a way that does not make NewPipe crash after import. Though that’s probably a separate bug report.

@Profpatsch Profpatsch added feature request Issue is related to a feature in the app needs triage Issue is not yet ready for PR authors to take up labels Jan 26, 2025
@ShareASmile ShareASmile added database Issue and PRs related to database operations and removed needs triage Issue is not yet ready for PR authors to take up labels Jan 26, 2025
@Stypox
Copy link
Member

Stypox commented Feb 5, 2025

Well if PipePipe changed the DB format there is not much we can do. Closing as won't fix, we can't try to import stuff and adapt to every possible fork's database out there. The solution to this would be something like https://github.com/UniversalPipeWrench, though the progress there is stale.

@Stypox Stypox closed this as completed Feb 5, 2025
@Stypox Stypox added the wontfix This issue will not be fixed label Feb 5, 2025
@Stypox Stypox closed this as not planned Won't fix, can't repro, duplicate, stale Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database Issue and PRs related to database operations feature request Issue is related to a feature in the app wontfix This issue will not be fixed
Projects
None yet
Development

No branches or pull requests

3 participants