Skip to content

Conversation

@Nolwennig-Jeulin
Copy link

@Nolwennig-Jeulin Nolwennig-Jeulin commented Nov 4, 2025

Change value_id column to be unsigned in db_schema.xml to prevent SQLSTATE[22003]: Numeric value out of range: Out of range value for column 'value_id'

SHOW TABLE STATUS LIKE 'catalog_product_entity_varchar' \G
*************************** 1. row ***************************
            Name: catalog_product_entity_varchar
          Engine: InnoDB
         Version: 10
      Row_format: Dynamic
            Rows: 12955092
  Avg_row_length: 64
     Data_length: 840728576
 Max_data_length: 0
    Index_length: 710082560
       Data_free: 6291456
  Auto_increment: 2147485826
     Create_time: 2022-03-06 05:26:46
     Update_time: 2025-11-03 08:43:28
      Check_time: NULL
       Collation: utf8mb3_general_ci
        Checksum: NULL
  Create_options:
         Comment: Catalog Product Varchar Attribute Backend Table
Max_index_length: 0
       Temporary: N
1 row in set (0.002 sec)

Questions or comments

Under what conditions can an auto_increment value be negative?

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

unsigned primary key for tables catalog_product_entity_*
@m2-assistant
Copy link

m2-assistant bot commented Nov 4, 2025

Hi @Nolwennig-Jeulin. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:
  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.


For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@ct-prd-pr-scan
Copy link

ct-prd-pr-scan bot commented Nov 4, 2025

The security team has been informed about this pull request due to the presence of risky security keywords. For security vulnerability reports, please visit Adobe's vulnerability disclosure program on HackerOne or email [email protected].

@Nolwennig-Jeulin
Copy link
Author

@magento run all tests

@ct-prd-pr-scan
Copy link

ct-prd-pr-scan bot commented Nov 4, 2025

The security team has been informed about this pull request due to the presence of risky security keywords. For security vulnerability reports, please visit Adobe's vulnerability disclosure program on HackerOne or email [email protected].

@Nolwennig-Jeulin
Copy link
Author

@adobe/open-source-office Adobe CLA is signed

@Nolwennig-Jeulin
Copy link
Author

usefull to fix #40269

@Nolwennig-Jeulin
Copy link
Author

close and re-open to check CLA again

@ct-prd-pr-scan
Copy link

ct-prd-pr-scan bot commented Nov 4, 2025

The security team has been informed about this pull request due to the presence of risky security keywords. For security vulnerability reports, please visit Adobe's vulnerability disclosure program on HackerOne or email [email protected].

2 similar comments
@ct-prd-pr-scan
Copy link

ct-prd-pr-scan bot commented Nov 4, 2025

The security team has been informed about this pull request due to the presence of risky security keywords. For security vulnerability reports, please visit Adobe's vulnerability disclosure program on HackerOne or email [email protected].

@ct-prd-pr-scan
Copy link

ct-prd-pr-scan bot commented Nov 4, 2025

The security team has been informed about this pull request due to the presence of risky security keywords. For security vulnerability reports, please visit Adobe's vulnerability disclosure program on HackerOne or email [email protected].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant