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

SQLite DB with package name only #21

Open
iloveitaly opened this issue Feb 15, 2025 · 4 comments
Open

SQLite DB with package name only #21

iloveitaly opened this issue Feb 15, 2025 · 4 comments

Comments

@iloveitaly
Copy link

Thoughts on creating a "thinner" DB with package names only.

Would help solve searching locally for this extension: raycast/extensions#16494

@orf
Copy link
Member

orf commented Feb 18, 2025

We could definitely add that, but if you just want the package names then a gzip-compressed JSON file might be simpler?

However, adding a stripped down and smaller SQLite database feels like it should have more than just the package names. Excluding the package URLs for example, or some of the larger columns. This would have 1 row per package version

@iloveitaly
Copy link
Author

More information would be great, this could make a much richer experience in the extension! Main issue is the size: 1.5GB is too much. Would hope the entire DB could be < 100mb or so. The more data that could fit into a much smaller size would be amazing!

@orf
Copy link
Member

orf commented Feb 19, 2025

What extra information would you be looking for, specifically?

@iloveitaly
Copy link
Author

The main goal would be providing a richer search experience. Right now, you can only search on words in a package title.

If we included:

  • Description
  • Keywords

We could enable full text search on these fields in SQLite for a richer search experience.

The version, homepage, etc information can be pulled using the pypi API so I'm not as worried about those. It's only the search experience that is impossible to replicate right now since there is no search API.

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

No branches or pull requests

2 participants