brittneybrinsfield / sequel-pro

Automatically exported from code.google.com/p/sequel-pro
Other
0 stars 0 forks source link

Running a query in the query editor does not reflect results obtained running from the command line #1841

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I run my query in the editor:

SELECT 
    `publications_bibliographicrecord`.`id`

FROM 
    `publications_bibliographicrecord` 
    INNER JOIN `publications_authored` ON (`publications_bibliographicrecord`.`id` = `publications_authored`.`bibliographic_record_id`) 
WHERE 
    `publications_authored`.`researcher_id` IN (
        SELECT 
            DISTINCT U0.`person_id` 
        FROM 
            `publications_researcher` U0 
            INNER JOIN `contacts_and_people_person` U1 ON (U0.`person_id` = U1.`personlite_ptr_id`) 
            INNER JOIN `contacts_and_people_membership` U2 ON (U1.`personlite_ptr_id` = U2.`person_id`) 
        WHERE 
            U2.`entity_id` IN (
                SELECT 
                    U0.`entitylite_ptr_id` 
                FROM 
                    `contacts_and_people_entity` U0 
                WHERE 
                    (U0.`lft` <= 204 AND U0.`lft` >= 3 AND U0.`tree_id` = 1 )
                )
        );

The MySQL database is on a remote server.

I expect to see similar times reported from both Sequel Pro and the MySQL 
shell, though I am not sure that this expectation is correct.

Sequel Pro reports: "30413 rows affected, taking 6.5ms"

Running the same query in the shell: "30413 rows in set (0.73 sec)"

Is this the time to execute the query, or to execute *and* report it?

If reporting time is included, that might explain the discrepancy.

Sequel Pro Build 4096 v. 1.0.2

OS X 10.9

MySQL Server version: 5.5.21

Original issue reported on code.google.com by dani...@vurt.org on 31 Oct 2013 at 2:28