The db:seed command invokes the root seeder DatabaseSeeder which can
invoke another seeders using the call() related methods. The root seeder
can be set by the --class command-line option and also by the --seeder
cmd. line option on some other commands like migrate:fresh/refresh.
Seeders can be passed to the Tom application in the similar way like the
migrations using the TomApplication::seeders<>() method or through the
constructor.
Arguments can be passed to the call<>() method, then the seeders run()
method will not be called using the virtual dispatch but using the type
traits. Of course the arguments passed to the call<>() method has to
match with the run() method parameters.
Others:
- unified usingConnection() across all commands, this functionality was
extracted to own class, previous it was a part of the Migrator class,
so now every command even if it doesn't use Migrator can call
the usingConnection() and it correctly sets a default connection and
SQL queries debugging on the base of the -vvv command-line argument
- a default database connection is now required, if not set then
the exception will be thrown
- added example seeders to the Tom application
Extracting these guard related methods to own class allows to call
GuardedModel::unguarded() regardless of a template parameters needed
on the Model class, before was needed to call
Model<Torrent, Relations..>::unguarded().
- also made the g_unguarded atomic
- bugfix reguard() try-catch-finally in GuardedModel::unguarded()
Renamed cmake option and macro from the TINY/TOM_MIGRATIONS_PATH to the
TINY/TOM_MIGRATIONS_DIR.
- updated documentation
- extracted init. code for the TINYTOM_MIGRATIONS_DIR to the own cmake
macro
They can now also set up include directories and link against
the TinyORM library. It's accomplished by the TINYORM_BUILD_TREE
variable.
- also updated all examples in the documentation
- manually tried to recompile all the examples on all supported
platforms
- enhanced tiny_version_numbers.prf, throw error when the version file
was not found or when the parsing failed
- used qmake/common.pri in the TinyOrm.pri and tom.pri,
the consequences are that the user can use eg "CONFIG += disable_orm"
and all others supported qmake configurations on his own project, so
if the TinyORM was compiled with some set of flags then the same set
of flags has to be used on the compiled project, CMake is doing this
automatically of course
- added Configure using .qmake.conf to the hello world example
silverqx