silverqx
|
a6213a6a9d
|
added migrations 🔥🚀✨
Almost everything is implemented, possible to migrate up, down
(rollback), migrate by steps (works for up/down too), reset, refresh,
fresh, wipe database, showing status, installing migration table.
Command line interface is superb, it supports ansi coloring, verbosity,
no-interactive mode, force option, env option to select current env.
It has enhanced ansi coloring (vt100 terminal) detection, when ansi or
no-ansi option is not passed it can detect whether terminal supports
coloring.
Ansi coloring is disabled when redirection to file is detected (can
be overridden by ansi/no-ansi options).
Supports NO_COLOR env. variable (https://no-color.org/) and can detect
the ConEmu, Hyper, and xterm on Windows.
Carefully implemented help and list commands, list command can print
supported commands by namespace.
Advanced make migration command offers great command interface for
creating migration classes, supports options for generating empty,
create, or update migration classes.
Unfinished make project command, will support creating qmake, qmake
subproject, and cmake, cmake subproject projects. Later will be
extracted to own executable tomproject.exe for rapidly generating a new
TinyORM projects.
Other implemented commands are env that prints current env. and inspire
that displays an inspiring quote 😁.
Verbose supports 5 levels quiet, normal, verbose, very verbose, and
debug.
Possibility to disable compilation of the tom command related code using
TINYORM_DISABLE_TOM c macro, for the qmake exists disable_tom CONFIG
option and for the CMake exist TOM configuration option.
Confirmable interface that ask Y/N confirmation during migrate when
env. == production, can be overridden by --force option.
Whole tom terminal application supports or is implemented with UTF-8
support, also implemented UTF-16 output methods but they are not needed.
Input also supports UTF-8, currently only Y/N input is needed by the
Confirmation concern.
All migrate commands also support the --pretend option and the --env
option, when env. is production then tom asks confirmation to migrate,
it can be overridden by the --force option.
Added the tom example project, it is a complete command-line migration
application, it uses migrations from the tests.
Implementing this was really fun 🙃😎.
- added 14 functional tests to test migrations up/down, stepping,
installing migration table, refresh, reset on MySQL database
- added unit test to check version number in tom.exe executable
- new tom exception classes
- created dozens of a new todo tasks 😂🤪, currently 348 todos 😎
- added some info messages to the qmake build about building features
- in the debug build and with the -vvv option enable debugging of sql
queries
- enhanced RC and manifest file generation, allowed to pass a custom
basename for a RC/manifest file as the 3. argument and a custom
replace token for the CMake genex as the 4. argument
- bugfix disabled #pragma code_page(65001) // UTF-8 in RC files, it
messes up the © character
Output of tom exe without arguments and options:
Common options:
--ansi Force ANSI output
--no-ansi Disable ANSI output
--env The environment the command should run under
-h, --help Display help for the given command. When no
command is given display help for the list
command
-n, --no-interaction Do not ask any interactive question
-q, --quiet Do not output any message
-V, --version Display this application version
-v|vv|vvv, --verbose Increase the verbosity of messages: 1 for normal
output, 2 for more verbose output and
3 for debug
Available commands:
env Display the current framework environment
help Display help for a command
inspire Display an inspiring quote
list List commands
migrate Run the database migrations
db
db:wipe Drop all tables, views, and types
make
make:migration Create a new migration file
make:project Create a new Tom application project
migrate
migrate:fresh Drop all tables and re-run all migrations
migrate:install Create the migration repository
migrate:refresh Rollback and re-run all migrations
migrate:reset Rollback all database migrations
migrate:rollback Rollback the last database migration
migrate:status Show the status of each migration
|
2022-04-20 15:45:35 +02:00 |
|