#database_config

[sachin156]

Blogs posted in PHP. The title is Using multiple database connections in CakePHP model - Find Nerd

In this blog, I am Showing methods to use multiple databases for development and for production without changing anything but rewriting a function in DATABASE_CONFIG class. For complete information visit my full Bloghttp://findnerd.com/list/view/Using-multiple-database-connections-in-CakePHP-model/3469/

[alexgenovese]

Cakephp 2.0.5 cake bake issue

Fatal error: Class 'DATABASE_CONFIG' not found...

1. Go to /path/to/cakephp/lib/Cake/Console/

2. Then write: ./cake bake -app "/Applications/MAMP/htdocs/cakephp/app/"

3. It works!

[brelsnok-blog]

"bake schema generate" env() problem

I spent some time on the following problem. It's more an explanation 'why', not so much a solution. I'm using CakePHP 1.3.4 and typically switch database configuration based on the `env('HTTP_HOST')` variable. In this specific case I diverted from my regular setup in which `$this->default` is the `localhost` database configuration and `$this->live` is the stage database configuration. Instead I switched those two. As I was calling `cake schema generate` I received errors telling me things like `PHP Warning: mysql_connect(): php_network_getaddresses: getaddrinfo failed: nodename nor servname provided, or not known in` and `Warning: mysql_select_db() expects parameter 2 to be resource, boolean given in` Clearly there was no database connection. I didn't detect anything weird when calling the site on `http://localhost`, it switched nicely based on the `env('HTTP_HOST')` variable. After some experimenting I discovered that having my `localhost` database config as the default config solved the problem. That pointed me to the fact that `env('HTTP_HOST')` is not present when calling `bake`. It's a server variable, and when running from the command line, the server doesn't play a role. By assigning the localhost config to the `$this->default` variable I can easily bypass the problem. Though I foresee a small inconvenience when working with multiple developers, committing to the same repository, that all have their own localhost test config.