Declarative schema bug : default value cannot be negative on signed int

[Nuranto]

Preconditions (*)

Magento 2.4.1

Steps to reproduce (*)

Create a table with thoses columns :

<column xsi:type="int" name="some_name" unsigned="false" nullable="false" identity="false" default="-1" comment="Some Name"/>

Note that unsigned is set to false.

Expected result (*)

Table is created

Actual result (*)

Element 'column', attribute 'default': [facet 'pattern'] The value '-1' is not accepted by the pattern '\d+|null'.

Additional Information

Attaching module which helps in issue reproduction:
Magz.zip

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround. (When migrating from M1 for instance)
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @Nuranto. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[Nuranto]

Still relevant

[m2-assistant]

Hi @engcom-Alfa. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Alfa]

HI @Nuranto
We have followed the steps that you have provided and we are not able to reproduce the issue. The table was created successfully , please refer the attached screenshot

[Nuranto]

Just tested again on Magento 2.4.2, and I still got :

The XML in file "/var/www/html/app/code/**/**/etc/db_schema.xml" is invalid:
Element 'column', attribute 'default': [facet 'pattern'] The value '-1' is not accepted by the pattern '\d+|null'.
Line: 17

Element 'column', attribute 'default': '-1' is not a valid value of the local atomic type.
Line: 17

Verify the XML and try again.

For some reason I don't understand, in your case, you probably didn't went through \d+|null (vendor/magento/framework/Setup/Declaration/Schema/etc/types/integers/integer.xsd) validation regexp, which do fail with negative value.

[gabrieldagama]

Hi @Nuranto, can you clarify on which action are you having the error? For example, I do get the XSD validation error on my PHPStorm, but if I try to run php bin/magento setup:db-schema:upgrade it does work and the column is added.

Maybe you can clarify and add more details on the step to reproduce the problem?

Thanks.

[Nuranto]

I got it while running setup:upgrade.
I have obviously the same error when running setup:db-schema:upgrade, but with a trace. Here it is if that can helps :

#0 /var/www/html/vendor/magento/framework/Config/Reader/Filesystem.php(132): Magento\Framework\Config\Reader\Filesystem->_readFiles(Array)
#1 /var/www/html/vendor/magento/framework/Setup/Declaration/Schema/Declaration/ReaderComposite.php(46): Magento\Framework\Config\Reader\Filesystem->read('all')
#2 /var/www/html/vendor/magento/framework/Setup/Declaration/Schema/SchemaConfig.php(76): Magento\Framework\Setup\Declaration\Schema\Declaration\ReaderComposite->read('all')
#3 /var/www/html/setup/src/Magento/Setup/Model/DeclarationInstaller.php(57): Magento\Framework\Setup\Declaration\Schema\SchemaConfig->getDeclarationConfig()
#4 /var/www/html/setup/src/Magento/Setup/Model/Installer.php(846): Magento\Setup\Model\DeclarationInstaller->installSchema(Array)
#5 /var/www/html/setup/src/Magento/Setup/Model/Installer.php(894): Magento\Setup\Model\Installer->declarativeInstallSchema(Array)
#6 /var/www/html/setup/src/Magento/Setup/Console/Command/DbSchemaUpgradeCommand.php(83): Magento\Setup\Model\Installer->installSchema(Array)
#7 /var/www/html/vendor/symfony/console/Command/Command.php(255): Magento\Setup\Console\Command\DbSchemaUpgradeCommand->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#8 /var/www/html/vendor/symfony/console/Application.php(1009): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#9 /var/www/html/vendor/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand(Object(Magento\Setup\Console\Command\DbSchemaUpgradeCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#10 /var/www/html/vendor/magento/framework/Console/Cli.php(115): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#11 /var/www/html/vendor/symfony/console/Application.php(149): Magento\Framework\Console\Cli->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#12 /var/www/html/bin/magento(23): Symfony\Component\Console\Application->run()
#13 {main} [] []

Here is my db_schema.xml schema and table tags :

<?xml version="1.0"?>
<schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="urn:magento:framework:Setup/Declaration/Schema/etc/schema.xsd">
    <table name="table_name" resource="default" engine="innodb" comment="Table comment">

Is it the same as yours ?

I don't know what else could differs...

PHP version : 7.4.12, running on a Docker php:7.4-apache based image.