Implement typeTinyint for SQLite grammar

[Mrkbingham]

The compileChange override in vendor/winter/storm/src/Database/Schema/Grammars/SQLiteGrammar.php reads SQLite column type names as tinyint (from SQLite metadata for boolean columns), then calls getType() which looks for ->typeTinyint(... — but only typeTinyInteger exists in the base grammar file Illuminate\Database\Schema\Grammars\SQLiteGrammar.

This should resolve migration issues others might hit when upgrading to 1.3

Summary by CodeRabbit

• Bug Fixes

  • SQLite schema operations now correctly handle tinyint column types, eliminating errors during column introspection and reconstruction.

• Tests

  • Added validation tests for tinyint column type mapping in SQLite, ensuring proper SQL generation for schema operations.

[mjauvin]

Would it be possible to submit a test case for this?

[Mrkbingham]

@mjauvin added a test!

[mjauvin]

Thanks for adding the unit-test, however if I remove the typeTinyHint() method the test still passes.

[LukeTowers]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Mrkbingham]

@mjauvin I went back and double-checked, I'm still getting this error when running PHPUnit tests in my WinterCMS app as well as the test case I wrote here. I'm running SQLite v3.51.0, not sure if it's a version issue.

I suppose as an alternative to lend more support downwards into Laravel rather than patching it here could be to just add a match statement on line 47:

'type' => match($column['type_name']) {                                                                                                                                    
      'tinyint'  => 'tinyInteger',
      default    => $column['type_name'],                                                                                                                                    
  }, 

Happy to provide more details if there's anything you're curious about here. Also thanks for getting Coderabbit to review this @LukeTowers !

[mjauvin]

@mjauvin I went back and double-checked, I'm still getting this error when running PHPUnit tests in my WinterCMS app as well as the test case I wrote here. I'm running SQLite v3.51.0, not sure if it's a version issue.

I suppose as an alternative to lend more support downwards into Laravel rather than patching it here could be to just add a match statement on line 47:

'type' => match($column['type_name']) {                                                                                                                                    
      'tinyint'  => 'tinyInteger',
      default    => $column['type_name'],                                                                                                                                    
  }, 

Happy to provide more details if there's anything you're curious about here. Also thanks for getting Coderabbit to review this @LukeTowers !

You may be right, the environment where I tested it uses an older SQLite version (v3.31.1).

[mjauvin]

@LukeTowers any idea what all those unit-test errors are?

[LukeTowers]

@mjauvin these test failures look unrelated, I'll merge it into 1.3 now and will work on getting 1.3 up to date along with Laravel 13 support next week.