Fabian Lange
14 days ago
Living on the edge
6
Today Propel 1.4 was released and it contains some debugging goodies.
We can use the DebugPDO class to get the nifty logging into the Web Debug Panel. However some more interesting information is turned off by default by Propel.
It includes:
- Time logging
- Time spent for executing this query
- Memory logging
- Peak Usage during execution of the query
- Total Memory usage after the query ran
- Memory Delta caused by executing the query
- Slow query logging
- Duration after which a query is considered slow
Using this is very easy as of today / symfony 1.3 beta 2:
dev:
propel:
param:
classname: DebugPDO
debug:
realmemoryusage: true
details:
time:
enabled: true
slow:
enabled: true
threshold: 0.001
memdelta:
enabled: true
mempeak:
enabled: true
method:
enabled: true
mem:
enabled: true
querycount:
enabled: true
The whole list can be found in the Propel Documentation. The prefix debugpdo.logging is taken care of by the key debug. Simply put the remaining path below it, creating a new nesting level each dot.
Because Propel takes the order into account, the above configuration results into something like this:
Add a Comment
Comments 
-
#1 M said about 1 hour later

"Time logging", "Memory logging", "Slow query logging"
AWESOME! :)
-
#2 BabyWolf said about 10 hours later

Very good!
-
#3 Marco Schierhorn said about 13 hours later

Awesome.Thats what I call a DB Debug Toolbar
-
#4 Disco Zohan said about 20 hours later

Will doctrine 1.2 provide some functionality like this?
P.s. with symfony 1.2 + doctrine 1.1 there are just queries, even without execution time .. -
#5 Titang said 3 days later

I was looking for this for a long time! That's a really great tool for debuging/optimization
-
#6 Etienne Bohm said 11 days later

I thought propel was no longer supported on symfony.
I think Propel is a very good ORM.
Can we still use it for new project?





