Hi,

On Fri, May 23, 2014 at 12:52 AM, Marc Delisle <marc@infomarc.info> wrote:
Chirayu Chiripal a écrit :
> On Fri, May 23, 2014 at 12:35 AM, Marc Delisle <marc@infomarc.info> wrote:
>
>> Chirayu Chiripal a écrit :
>>> Hi,
>>>
>>> While analyzing the current behavior of export feature, few doubts has
>>> arisen in my mind regarding it. In sql_export.png, There are two export
>>> buttons, button 1 & button 2 respectively. When exporting using Button 1
>>> shown in sql_export.png, the resulting sql file had all the rows (20
>> rows)
>>> present in the table (See QA_4_2_Button_1_export.sql) whereas when
>> Button 2
>>> was used then only the rows (10 rows) displayed in results according to
>> the
>>> LIMIT condition in the query were in the sql file (See
>>> QA_4_2_Button_2_export.sql). Is this the correct behavior or both should
>>> have generated identical sql export file?
>>>
>>> SQL query which was used: SELECT * FROM `abcd` WHERE 1 limit 10
>>>
>> Button 1 means to export the rows that you have selected via each row's
>> checkbox.
>>
>> --
>> Marc Delisle (phpMyAdmin)
>>
>
> What if I didn't selected any rows?
>
> IMHO, In this case it should not export rows which are not in the resultset
> of the query but it is exporting all the rows of the table.

Correct, it should not export anything.

--
Marc Delisle (phpMyAdmin)
 
 
Currently, there is no SQL Export for queries involving multiple tables such as join query. So, does that mean aliases is to be considered only in SELECT statements involving one table? or Am I missing something here?

--
Regards,
Chirayu Chiripal
phpMyAdmin Intern - Google Summer of Code 2014
https://chirayuchiripal.wordpress.com/