Not signed in (Sign In)

Vanilla 1.1.5a is a product of Lussumo. More Information: Documentation, Community Support.

  1.  
    Hello,

    Thank you for creating an excellent product. Truly amazing!

    One feature request is that you allow the program to store the full queries with all parameter variables in-tact as an option, I can re-run the query exactly as i would in my application.. as this sometimes will give very different results in the 'explain' box.

    Kind Regards
  2.  
    Glad to hear you like Jet Profiler, pitstopboss! Regarding full queries, the current "?=1" parameter substitution was really a fast workaround, just to get something out. We're now changing it so it will store full queries - the slowest example of every query. This will obviously give more accurate results.

    Hopefully, that feature should arrive with the next release! On a side note, we're also adding query rewriting so you can run EXPLAIN for UPDATE:s and DELETE:s too.

    Thanks for your input!
  3.  
    Update: this feature has now been released in version 0.9.9.
    • CommentAuthorpadys
    • CommentTimeFeb 17th 2009
     
    I have problem with EXPLAINing unions like that:

    (select ...)
    union
    (select ...)
    union
    (select ...)
    order by ...

    Jet Profiler shows only message "Invalid query / Only SELECTs can be explained".
  4.  
    The Explain dialog has a simple security filter which only allows well-formed queries, so that you do not accidentally run updates or inserts on the database. But sometimes, it doesn't recognize the query correctly. Try removing the parentheses and it should work better, e.g.

    select ...
    union
    select ...
    union
    select ...
    order by ...

    We're going to improving the filter, so hopefully it will work better in a future release (no date yet).
  5.  
    Not sure if this has been worked on yet, but....

    can you perhaps make suggestions for new indexes in the EXPLAIN area.
    maybe as an option... this can really make this product stand out if you nail this.

    many users of mysql are not of a high standard to understand about the best use of indexes and how to optimise them.
    this addition would make this product a must have for any level of database designer (it doesn't have to be perfect - just analyze based on the queries to that table the profiler can see in it's history, for example).

    I hope you can get back to me on this.
    • CommentAuthorsatish71
    • CommentTimeAug 18th 2009
     
    I had recently got this tool for my team, they are mightily pleased with it. I have a feature request for enticing a novice MYSQL developer - If your tool can provide expert guidance like "Created Indexes on XYZ columns to avoid Full Table Scan" or Suggest Alternative Queries if the Join size is huge etc...
  6.  
    Hello,

    glad to hear your team likes the tool!

    Thanks for the suggestions. We're definitely going to look deeper into this - adding some sort of query optimization or index suggestion tool. It's a complicated subject though, so it might take a while to develop.
  7.  
    Just adding a comment, I'm getting "Only Selects can be explained" with a simple query containing the NAME_CONST function.

    NAME_CONST('_id',233039)
  8.  
    linuxrunner, do you suppose you could show the complete query where the NAME_CONST() function appears?
  9.  
    padys, (SELECT...) union (SELECT...) should now be explainable.