A way to debug errors in Query Easily about aura.sql

[pmjones]

We kind of do this now with the profiler/logger. When the profiler is turned on, it captures the query text, the data bound to the query, the elapsed time, and (something i really like) a debug backtrace so you can see exactly where the query came from in the codebase. Is that sufficient?

[harikt]

When profiler is active , yes we get the query like the one below .

foreach($sql->getProfiler()->getProfiles() as $i => $profile ) {
    echo "Query : " . ($i+1) . "  " . $profile->text . " took " . $profile->time . PHP_EOL;
    //print_r( $profile->trace );
}

Query : 2  SELECT * FROM posts took 0.00012612342834473
Query : 3  SELECT * FROM posts Where id = :id took 0.00043177604675293
Query : 4  INSERT INTO `posts`(`title`, `author_id`, `body`) VALUES (:title, :author_id, :body) took 0.050559043884277

Problems are which I love to improve when profiler is setActive are :

1 ) You can see we cannot directly copy and paste the code and do a query some where .

So the query

  SELECT * FROM posts Where id = :id

will become

  SELECT * FROM posts Where id = 1

something like that.

2 ) Debug backtrace is an array of recursion. So when we do a print for it, that will be hard to trace it out . Is there an easy way ? May be I am missing all the functionality .