Greedings I am Dimitrios Desyllas aka pc_magas.
I am a php software engineer in e-table.
I am interested in privacy enhancing technologies, cryptography and reverse engineering.
Location
Acharnes, Greece
Education
MSc at Digital Systems Security at Univercity Of Peireus
Pronouns
Yo Wazz up bro!
Work
Volunteer Sysadmin at ELLAK of Cyprus - open for opportunities.
Greedings I am Dimitrios Desyllas aka pc_magas.
I am a php software engineer in e-table.
I am interested in privacy enhancing technologies, cryptography and reverse engineering.
Location
Acharnes, Greece
Education
MSc at Digital Systems Security at Univercity Of Peireus
Pronouns
Yo Wazz up bro!
Work
Volunteer Sysadmin at ELLAK of Cyprus - open for opportunities.
By setting the test database, nope I am unable to run the migrations.
The cause is that the postgresql database I am using actually keeps the columns into the table even if I delete it from the table and just hides it from the user.
The solution is to reconstruct the test database. So how I can prepend my existing migrations with one that generates the database?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Try to specify your pre-existing schema in the phpunit.xml config file.
Make sure you have backup of that db before running the test. Laravel's
DatabaseMigrationstrait will drop everything and re-migrate.I have tried that and I still get the error.
Are you able to run that migration outside of the test?
By setting the test database, nope I am unable to run the migrations.
The cause is that the postgresql database I am using actually keeps the columns into the table even if I delete it from the table and just hides it from the user.
The solution is to reconstruct the test database. So how I can prepend my existing migrations with one that generates the database?