Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The result of UNCOMPRESSED_LENGTH is different with MySQL #59617

Open
Tracked by #59410
YangKeao opened this issue Feb 18, 2025 · 0 comments
Open
Tracked by #59410

The result of UNCOMPRESSED_LENGTH is different with MySQL #59617

YangKeao opened this issue Feb 18, 2025 · 0 comments
Labels
severity/minor sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.

Comments

@YangKeao
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

SELECT UNCOMPRESSED_LENGTH('invalid_compressed_data')

2. What did you expect to see? (Required)

MySQL returns 561409641

3. What did you see instead (Required)

TiDB returns 1635151465.

4. What is your TiDB version? (Required)

@YangKeao YangKeao added severity/minor type/bug The issue is confirmed as a bug. labels Feb 18, 2025
@jebter jebter added the sig/sql-infra SIG: SQL Infra label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/minor sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

2 participants