Open legecha opened 8 years ago
Can you please show propel.php? The DSN is important.
'dsn' => 'mysql:host=localhost;port=3306;dbname=leonard_returns',
Can you please try using the database:reverse
command? If this is working fine, then init
is the issue.
Thanks @marcj, this led me to looking at the init command. Long story short, I found that in /tmp
there already exists a file called schema.xml
owned by another user, and I can confirm the content of this file matches what I found in my own schema.xml
.
I removed the file and ran init again in its entirety and it worked as expected.
Is it worth having some form of check in there to see if it can be written to and/or clean up afterwards?
Is someone able to make a PR here with suggested changes?
I'm expecting this to be down to my environment but I can't figure out why it's happening. After successfully running through
propel init
I am left with the following:propel.php
is exactly as you'd expect - the correct credentials.schema.xml
, however, shows the definition for a different database! I wondered if maybe propel was running from somewhere else?This seems OK. The schema it has details for is actually for a project located at
/var/www/subdomains/commitr
and has it's own unique credentials.The values in
propel.php
are for userle_returns
, and to confirm:But this is the output in
schema.xml
in the same folder:Hence:
Finally:
None of these locations exist or contain propel.
Any ideas why propel is working on the wrong database?