On 23/07/16 08:16, Richard Hipp wrote: > Draft change log: https://www.sqlite.org/draft/releaselog/3_14_0.html
Please please don't make the new trace/profile API expand the SQL by default. There are two problems with expanding by default: - The text no longer matches what the programmer had in their code. You can't grep for what trace reports if it is always expanded. Heck you can't even tell if two queries are the same except the bound parameters without fairly sophisticated parsing. It is best practise to use bound parameters and it should be encouraged, so penalising that is unhelpful. - It consumes considerably more memory and cpu, which makes it less likely to be something you normally use. That significantly decreases the value of the feature versus using it most of the time. Essentially it is a one way un-reversible conversion of what the programmer wrote, and hence significantly less helpful. Roger
signature.asc
Description: OpenPGP digital signature
_______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
