magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.
http://www.magento.com
Open Software License 3.0
11.59k stars 9.32k forks source link

Database tables with primary column having signed instead of unsigned definition which is loss of usable values #38585

Open kanevbg opened 8 months ago

kanevbg commented 8 months ago

Preconditions and environment

Steps to reproduce

There is nothing to reproduce, it's a theoretical, architectural problem.

Expected result

Not applicable.

Actual result

Not applicable.

Additional information

Table catalog_product_entity_text has value_id primary column defined as signed int. However the system never stores zero or negative ID in that table. image.

This means we have 50% usable values of what the underlining database storage may store in practice for the data produced by the application. I have not found a single reason for that column being signed instead of unsigned. Please checkout.

This is applicable to the following tables:

Release note

No response

Triage and priority

m2-assistant[bot] commented 8 months ago

Hi @kanevbg. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

faizanps commented 8 months ago

@magento give me 2.4-develop instance

magento-deployment-service[bot] commented 8 months ago

Hi @faizanps. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 8 months ago

Hi @faizanps, here is your Magento Instance: https://0e41f955810ef54252bf938113d242f0.instances-prod.magento-community.engineering Admin access: https://0e41f955810ef54252bf938113d242f0.instances-prod.magento-community.engineering/admin_7857 Login: cfa74781 Password: 3060e70b5a2a

kanevbg commented 8 months ago

@Bashev адаш така е нали 😄

faizanps commented 8 months ago

@magento give me 2.4-develop instance

magento-deployment-service[bot] commented 8 months ago

Hi @faizanps. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 8 months ago

Hi @faizanps, here is your Magento Instance: https://0e41f955810ef54252bf938113d242f0.instances-prod.magento-community.engineering Admin access: https://0e41f955810ef54252bf938113d242f0.instances-prod.magento-community.engineering/admin_425c Login: 016dfea5 Password: 2e3132a39f56

m2-assistant[bot] commented 8 months ago

Hi @engcom-Dash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:


engcom-Dash commented 7 months ago

Hi @kanevbg

Thanks for reporting and collaboration.

Verified the issue in magento 2.4 dev instance. The issue is reproducable.

Database tables with primary column having signed instead of unsigned definition. Hence, confirming the issue.

Please refer the attached screenshots.

Screenshot 2024-04-10 at 7 09 02 PM
github-jira-sync-bot commented 7 months ago

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-11758 is successfully created for this GitHub issue.

m2-assistant[bot] commented 7 months ago

:white_check_mark: Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

kanevbg commented 7 months ago

@engcom-Dash Please let me know if additional assistance or information may be helpful from my side.

KrasnoshchokBohdan commented 4 months ago

@magento I am working on this