You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't understand it well, so I put echo __CLASS__,'::',__FUNCTION__,':',__LINE__,PHP_EOL;
in many places and executed it, and the result is as follows.
Phalcon\Migrations\Console\Commands\Migration::run:102
Phalcon\Migrations\Migrations::run:387
Phalcon\Migrations\Mvc\Model\Migration::migrate:317
CompaniesMigration_100::afterCreateTable:115
Phalcon\Migrations\Mvc\Model\Migration::batchInsert:800
/srv/vendor/phalcon/migrations/src/Mvc/Model/Migration.php:903:
string(178) "INSERT INTO companies (id,name,telephone,address,city) VALUES ('1','Acme','31566564','Address','Hello'),('2','Acme Inc ','+44 564612345','Guildhall, PO Box 270, London','London');"
Phalcon\Migrations\Mvc\Model\Migration::migrate:324
CompaniesMigration_100::up:88
Phalcon\Migrations\Mvc\Model\Migration::batchInsert:800
/srv/vendor/phalcon/migrations/src/Mvc/Model/Migration.php:903:
string(178) "INSERT INTO companies (id,name,telephone,address,city) VALUES ('1','Acme','31566564','Address','Hello'),('2','Acme Inc ','+44 564612345','Guildhall, PO Box 270, London','London');"
It seems that afterCreateTable() and up() are called in succession in Migration::migrate.
(each calling batchInsert() )
Is this because these two are defined in companies.php?
Or is it a bug in phalcon/migrations?
The text was updated successfully, but these errors were encountered:
I did the following for the migration.
Then the following message is displayed.
I don't understand it well, so I put
echo __CLASS__,'::',__FUNCTION__,':',__LINE__,PHP_EOL;
in many places and executed it, and the result is as follows.
It seems that afterCreateTable() and up() are called in succession in Migration::migrate.
(each calling batchInsert() )
Is this because these two are defined in companies.php?
Or is it a bug in phalcon/migrations?
The text was updated successfully, but these errors were encountered: