fix: #27138, stream with 64-bit PK

[cocowalla]

Resolves an issue with blob streaming, where a 32-bit PK was always expected - but SQLite stores integers as signed, 64-bit values.

• SqlDataRecord.GetStream changed from using GetInt32 to GetInt64
• Added a new test

Fixes #27138

[cocowalla]

@bricelam a couple of the CI jobs are failing, but it looks to be an issue with the CosmosDB emulator in the pipeline, AFAICS.

[bricelam]

The CI has been a bit flakey. The test passed on Linux, Windows, and macOS, so I'm comfortable merging it.

[smitpatel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[smitpatel]

I am not comfortable merging on failing CI at least unless it fails on multiple attempts. We broke main branch with SqlClient upgrade by ignoring CI failure.

[bricelam]

Rebased on main. Updated the test to cover uint values too.

[ghost]

Hello @bricelam!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[cocowalla]

I am not comfortable merging on failing CI at least unless it fails on multiple attempts. We broke main branch with SqlClient upgrade by ignoring CI failure.

It looks like it has failed the same way on 2 attempts - I think @ajcvickers manually kicked on the 2nd rerun.

[ghost]

Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:

1. Azure Pipelines

These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check.

Give feedback on this

From the bot dev team

We've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments.

Please reach out to us at [email protected] to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin.

[bricelam]

CI seems to be succeeding today. I bet the rebase will let it pass this time.

[bricelam]

These integrations are possibly never going to report a check...

Wow msftbot, have you been hanging around Marvin or something?

[bricelam]

@cocowalla Thank you for your contribution! It should be available in the daily builds soon, and in 7.0 Preview 1 whenever that ships (probably February).