From 37c1f43908dd26b58272e22aa50f369757747e62 Mon Sep 17 00:00:00 2001 From: Manu Ganji Date: Thu, 22 May 2014 16:25:23 +0530 Subject: Update profiling.rst There is some confusion about how to enable profiling for queries. This will save some time for devs who want to debug their generated SQL. --- user_guide_src/source/general/profiling.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'user_guide_src') diff --git a/user_guide_src/source/general/profiling.rst b/user_guide_src/source/general/profiling.rst index f29af8102..4945b39b3 100644 --- a/user_guide_src/source/general/profiling.rst +++ b/user_guide_src/source/general/profiling.rst @@ -82,6 +82,8 @@ Key Description hidden. ======================= =================================================================== ======== -.. note:: Disabling the **save_queries** setting in your database configuration +.. note:: Disabling the [save_queries](http://ellislab.com/codeigniter/user-guide/database/configuration.html) setting in your database configuration will also effectively disable profiling for database queries and render - the 'queries' setting above useless. \ No newline at end of file + the 'queries' setting above useless. You can optionally override this + setting with `$this->db->save_queries = TRUE;`. Without this setting you + won't be able to view the queries or the [last_query](http://ellislab.com/codeigniter/user-guide/database/helpers.html). -- cgit v1.2.3-24-g4f1b