Update dependency linq2db.SqlServer to v6#37
Conversation
|
🚀 AI Library Upgrade workflow started Checkout and dependency detection in progress. You will see further updates as each step completes. |
|
📋 Detected Library Changes Relevant dependency changes were detected. Specialized scans will be initiated shortly. Direct Dependency Changes
|
|
🔬 Library scan started Scanning source branch libraries for upgrade analysis. This may take a few minutes. |
|
Specialized scan preparation produced no scannable library artifacts ( Workflow behavior for this PR:
|
|
🚀 Starting AI implementation... Beginning implementation of library upgrade changes. This may take several minutes. Workflow Status
|
AI Library Upgrade (empty scan artifacts)Immediate fallback Ticket generation was skipped because specialized scan artifacts could not be downloaded. Proceeding to attempt AI implementation based on the PR diff using the fallback path.
Documentation: https://docs.codelogic.com/Send_Build_Info/ |
The linq2db.SqlServer package v6.2.1 is a scaffolding package (T4 templates) that requires the main linq2db package to be referenced separately for runtime functionality. Added linq2db v6.2.1 to Directory.Packages.props and updated Dapper.Tests.Performance.csproj to reference both packages. The main linq2db package v6.2.1 supports .NET Framework 4.6.2+ and .NET Standard 2.0+, ensuring compatibility with all target frameworks used in this project.
✅ AI Library Upgrade Workflow CompleteWorkflow Status
Result: Changes Successfully Implemented✅ The AI has successfully implemented the library upgrade changes and pushed them to this PR. Summary:
Please review the changes and ensure they meet your requirements. Generated by CodeLogic AI Library Upgrade |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
garrmark
left a comment
There was a problem hiding this comment.
make improvements using the new features of the library
garrmark
left a comment
There was a problem hiding this comment.
make improvements using the new features of the library
|
🔧 PR review feedback detected, triggering improvement cycle... A review comment was received. The AI will apply the feedback and perform cleanup updates. Improvement Cycle Status
|
|
🚀 Starting AI improvement iteration... Applying the latest human review feedback to this PR. |
This commit modernizes the linq2db benchmark code to use v6+ recommended patterns and removes deprecated APIs: Changes: - Replace deprecated DataConnection.DefaultSettings with DataOptions pattern - Update Linq2DBContext to use DataOptions constructor (v6+ recommended) - Remove obsolete Linq2DBSettings and ConnectionStringSettings classes - Use fluent UseSqlServer() configuration method Benefits: - Aligns with linq2db v6 best practices and performance optimizations - Simplifies configuration by removing custom ILinqToDBSettings implementation - Leverages v6's improved connection management and reduced stack usage - Prepares codebase for future linq2db enhancements The new DataOptions pattern is the recommended approach in linq2db v6+ for configuring database connections, replacing the legacy DefaultSettings API which has been deprecated. References: - https://github.com/linq2db/linq2db/wiki/Linq-To-DB-6 - https://linq2db.github.io/articles/get-started/asp-dotnet-core/
✅ AI Library Upgrade Workflow CompleteWorkflow Status
Result: Changes Successfully Implemented✅ The AI has successfully implemented the library upgrade changes and pushed them to this PR. Summary:
Please review the changes and ensure they meet your requirements. Generated by CodeLogic AI Library Upgrade |
This PR contains the following updates:
5.4.1.9→6.2.1Release Notes
linq2db/linq2db (linq2db.SqlServer)
v6.2.1: Release 6.2.1This release contains only bugfixes.
Release notes
Nugets
Full Changelog: linq2db/linq2db@v6.2.0...v6.2.1
v6.2.0: Release 6.2.0Release highlights:
SQLisitors, could be managed using
LinqToDB.Common.Configuration.TranslationThreadMaxHopCountsetting~operator translation for all databasesCountBy,Index,MaxBy,MinBy,ExceptBy,UnionBy,IntersectByNVARCHAR2type mappingJSONandVECTORtypesClickHouse.Driverv0.9 and v1.0 provider versions. For v1.0+ provider we recommend to setReadStringsAsByteArrays=trueprovider optionRelease notes
Nugets
Full Changelog: linq2db/linq2db@v6.1.0...v6.2.0
v6.1.0: Release 6.1.0Release highlights:
LeftJoinandRightJoinoperatorsRelease notes
Nugets
Full Changelog: linq2db/linq2db@v6.0.0...v6.1.0
v6.0.0: Release 6.0.0Since previous release candidate final release contains following changes:
Linq To DBreleasesDataConnectionclass now available forDataContext-based contexts tooDistinctBysupportstring.Jointranslation and better translation ofSql.ConcatStringsandSql.StringAggregatecallsProvider-specific changes:
ORA-01704 string literal too longerrors on big LOB parametersVECTORtype support including mappings tofloat[]and mappings for vector functionsSystem.Data.SQLite2 provider supportFor full list of changes check this page
Release notes
Nugets
New Contributors
Full Changelog: linq2db/linq2db@v5.4.1...v6.0.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.