I had this issue back in November and it was fixed on the doctrine
side. I recently updated Symfony from 1.4.3 to the latest 1.4.7 and
the issue has cropped back up again. Even though I'm specifying two
different databases to use, it's still using the last one in the
list. The base models haven't changed and still bind correctly.
databases.yml:
all:
db1:
class: sfDoctrineDatabase
param:
dsn: 'mysql:host=localhost;dbname=db1'
username: db1
password: db1
db2:
class: sfDoctrineDatabase
param:
dsn: 'mysql:host=localhost;dbname=db2'
username: db2
password: db2
So even though the model says to bind to db1, it will return an error
now with can't find table db2.tableInDB1. The only change on my end
was a svn update in the vendor directory and then clear out cache.
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
