Revised the application description in README.md to specify the use of direct SQL queries with Dapper for saving and retrieving Vectors. The note about using Entity Framework Core has been moved and rephrased for better clarity.
Expanded the Vector support requirement to include both Azure SQL Database and Managed Instance, both currently in EAP. Improved wording for clarity in the note about using direct SQL queries with Dapper.
The README.md file has been updated to include a new note about how vectors are saved and retrieved using direct SQL queries with Dapper. Additionally, it provides a link to the master branch for those who prefer to use Entity Framework Core instead. This addition helps clarify the technologies used and offers options for different preferences.
Updated README.md for clarity and additional setup instructions:
- Refined repository description to highlight native Vector type.
- Rephrased note on Vector Support feature for readability.
- Removed mention of EFCore.SqlServer.VectorSearch library.
- Added instructions for updating VECTOR column size and setting Dimension property.
Added comment in Scripts.sql to guide vector size setting in Embedding column.
Cleaned up VectorSearchService.cs by removing unused and commented-out SQL command execution code.
- Updated README.md with details on Vector Support in Azure SQL Database, application functionalities, and setup instructions.
- Removed inheritance of `Question` class from `Search` class and deleted `Search` class.
- Minor adjustment in Program.cs for endpoint description consistency.
- Simplified appsettings.Development.json by removing the empty "ConnectionStrings" section.
- Enhanced Script.sql with SQL commands to create `DocumentChunks` and `Documents` tables, including schema for identifiers, content, embeddings, document names, creation dates, and established a foreign key relationship between the two tables.
Marco Minerva