Marco Minerva

Hi @dluc, Given that it is not possible to change the **x-delivery-limit** value after queue creation, I have added a `try... catch` block to log the error and throw an...

@dluc, GitHub signals that this PR has 1 change requested, but it seems that all the request changes have been addressed, or am I missing something?

Adding image and audio support will be definitively great. Unfortunately, in this moment I haven't the time to implement these new features. I'm happy to accept PR for this.

Sorry, I haven't undestood, can you explain better what do you mean? What kind of logging do you want to add?

OK, but what logging destination do you want to use?

At this moment, this feature is in Early Adopter Preview. I think the next step will be the Public Preview, but the timeline hasn't been shared yet. The PR with...

No problem, I'll continue to test the feature, I'm actively working with VECTOR type on SQL Azure. As of now, all the functional tests are green and I have made...

@dluc The new VECTOR type is now in Public Preview and available in Azure SQL Database for all users: https://devblogs.microsoft.com/azure-sql/exciting-announcement-public-preview-of-native-vector-support-in-azure-sql-database/. So, I think that we can resume this PR.

Thanks @vonzshik for the clarification! In the original implementation of Kernel Memory, the `NpgsqlDataSourceBuilder` and `NpgsqlDataSource` objects were created in the constructor of a class that is registered as **Singleton**...

Thank you for the exhaustive explanation @vonzshik. We have now reverted to the original connection handling and gave the suggestion of setting `Pooling=false` in the connection string whether pooling is...