Resolve multiple issues (#177)

| Fix Issue # | Fork PR # |
| ------ | ------ |
| #175 | SOHELAHMED7#36 |
| #172 | SOHELAHMED7#37 |
| #159  | SOHELAHMED7#39 |
| #158 | SOHELAHMED7#40 |
| #178 |
SOHELAHMED7#41 |

Author: cebe

.github/workflows/test.yml

@@ -20,7 +20,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        php-versions: ['7.2', '7.3', '7.4', '8.0', '8.1', '8.2', '8.3']
+        php-versions: ['7.4', '8.0', '8.1', '8.2', '8.3']
 
     # TODO use cache
     steps:

README.md

@@ -182,6 +182,8 @@ Such values are not allowed:
    - `int null default null after low_price` (null and default will be handled by `nullable` and `default` keys respectively)
    - MEDIUMINT(10) UNSIGNED ZEROFILL NULL DEFAULT '7' COMMENT 'comment' AFTER `seti`, ADD INDEX `t` (`w`)
 
+If `enum` and `x-db-type` both are provided then for database column schema (migrations), only `x-db-type` will be considered ignoring `enum`.
+
 ### `x-indexes`
 
 Specify table indexes
@@ -446,6 +448,8 @@ It works on all 3 DB: MySQL, MariaDb and PgSQL.
 
 Note: Changes in enum values are not very simple. For Mysql and Mariadb, migrations will be generated but in many cases custom modification in it are required. For Pgsql migrations for change in enum values will not be generated. It should be handled manually.
 
+It will be ignored for database column schema (migrations) if `x-db-type` is provided.
+
 ## Handling of `numeric` (#numeric, #MariaDb)
 
 precision-default = 10