Posts Categorized: Apple

According to Doctrine’s documentation, you should always utilize a Query Cache.

http://www.doctrine-project.org/documentation/manual/1_2/en/caching:query-cache-&-result-cache

You should always use query cache in a production environment. That said, you can easily use it during development, too. Whenever you change a DQL query and execute it the first time Doctrine sees that it has been modified and will therefore create a new cache entry, so you don’t even need to invalidate the cache.

That said, you need to add the following configuration options in

application.ini

If you have a standard Memcached running locally on port 11211 then the following should work.

resources.doctrine.manager.attributes.attr_query_cache.driver = memcache
resources.doctrine.manager.attributes.attr_query_cache.options.servers.host = localhost
resources.doctrine.manager.attributes.attr_query_cache.options.servers.port = 11211
resources.doctrine.manager.attributes.attr_query_cache.options.servers.persistent = true
resources.doctrine.manager.attributes.attr_query_cache.options.compression = false


Don’t store IP addresses in a database as a string like (192.168.10.10). That is just the human readable form of that number. You want to store it in the database as an integer.

MySQL has built in functions to handle converting a dot-notation ip address to an integer equivalent.


mysql> SELECT INET_ATON('192.168.0.10') AS ipn;
+------------+
| ipn |
+------------+
| 3232235530 |
+------------+

mysql> SELECT INET_NTOA(3232235530) AS ipa;
+--------------+
| ipa |
+--------------+
| 192.168.0.10 |
+--------------+


But, I needed this type of functionality in PHP itself. Long story short, I’m using Doctrine to handle the relationship that PHP has to the database and I need to convert the human readable dot-notation IP address to the integer style (unsigned integer that is).

PHP’s built in function ip2long comes close, but there is a little bit more to work the magic.

sprintf

is used to convert the signed integer to an unsigned one.

Ready to be inserted into the DB.

I’ve set up my project on a new server getting prepared to go live. With that comes, moving around some files getting things ready. One thing I’m working on it getting the Zend_Tool command line working.

On the server, I’ve configured

APPLICATION_ENV

to be

production

via

.htaccess

Problem

When I run

zf.sh show doctrine

it errors out because it’s trying to use my “development” DB config rather than the “production” one. I’m not sure how to get around this yet.

Solution

Not pretty, but you have to edit the source of the Zend Framework. The file to edit is
ZendFramework/library/Zend/Tool/Project/Context/Zf/BootstrapFile.php

Here is the diff for what needs to be changed.


--- BootstrapFile.php (saved version)
+++ (current document)
@@ -106,9 +106,11 @@
define('APPLICATION_PATH', $this->_applicationDirectory->getPath());
$applicationOptions = array();
$applicationOptions['config'] = $this->_applicationConfigFile->getPath();
+
+ $env = getenv('APPLICATION_ENV') ? getenv('APPLICATION_ENV') : 'development';

Then you need to add the APPLICATION_ENV environmental variable to your shell.

In OS X, I’ve found this to work:

Insert this at the end of your .bash_profile

declare -x APPLICATION_ENV="local"


Now you can declare an environment in application.ini that works for the Zend Tool (and ZFDoctrine in my case).

Zend Framework… awesome.
Doctrine ORB… awesome.

Both of these combined…. PURE AWESOME.

I set up a project just at it says to on this page http://github.com/fmntf/zf-doctrine. It took some doing, but I got it working and was quite happy with my initial results. Then I needed to start a new project, so I just copied all the files, tweaked the DB name was flying with a new project… with one caveat.

One of the modules I created using a YAML file was not getting created in the DB when I ran zf build-project doctrine --reload. It was frustrating, I tried changing a bunch of things.

In the end the whole problem was that the module folder didn’t have a controllers folder and that was it. So I created a controllers folder and then it created the corresponding tables in the db. I think this code has much to do with it

application/Bootstrap.php