If you've been following the development of this project, you might have noticed that there's been some discussion about supporting alternative database backends (#221, #247). After some tedious refactoring in #282, this is now really close to being released. There are a few things that I'd like to bring up, so that users can be more prepared about this upgrade.

1. There will be changes to the database configuration. If you've been running a standalone database backend and manually configured fields like db_url, hnsw, etc., you'd need to change your configuration. I'll post a more detailed guide after 1.0.0 is out, because I haven't finalised everything. Until then, it might be a good idea to pin the vectorcode version to "<1.0.0".
2. The initial 1.0.0 release will still come with only a chromadb 0.6.3 connector. I'll take a look at chromadb 1.x myself, and later other database backends. If you have development experiences with other vector database backends, you're more than welcome to take a look at the database submodule and help with implementing new database backends. Now that I've mostly completed the refactoring, I'll improve the documentation for developers to make it easier for people to contribute new database backends. Until the documentation is ready, you can always use the chromadb implementation as a reference.

Feel free to take a look at #282 (or build from source to give it a try) and leave some comments. It's always better to fix things before they're released.