Re: bzr commit into mysql-5.1-bugteam branch (nirbhay.choubey:3554) Bug#54899

[Nirbhay Choubey]

Hi Sergey,

On Friday 19 November 2010 04:07 PM, Sergey Vojtovich wrote:
> Nirbhay,
>
> On Fri, Nov 19, 2010 at 03:47:33PM +0530, Nirbhay Choubey wrote:
>    
>> Hi Sergey,
>>
>> I just wanted to put forward a 'valid' case where prompt and
>> database at command-line do not match (i.e. null vs test), but
>> still we do not filter statements.
>>
>> This is against the opinion that
>>
>> "queries to be accepted when one-database is
>> "test" and prompt says "test"."
>>      
> Yes, this is a valid case.
> What exactly in this case is against the opinon that "queries
> to be accepted when one-database is 'test' and prompt says 'test'."?
>    

mysql>   \R \d>
test>   drop database test;             # Query OK          -------->  Here prompt
> is test, (one-database is 'test') so no filtering required, the statement is executed
(none)>   select 1;                     # Outputs 1         -------->  Here prompt
is 'null' (one-database is 'test'), still we do not filter the statement.
(none)>   create database test;         # Query OK          --------->  Same as
above
(none)>   select 1;                     # Outputs 1         --------->  Same as
above
(none)>use test;                       # Database changed  --------->  Same as above
test>select 1;                         # Outputs 1         --------->  Here again
> the prompt is test, (one-database is 'test') so no filtering required, the statement is
> executed

This states that queries are accepted in this case too, when 
one-database is 'test'
and prompt is *not*  'test'.

So, if we decide to filter based on inequality of one-database and 
prompt, the
above valid case will not be possible.

Hope, I was able to answer your question.

Please let me know.

Regards,
Nirbhay


> Regards,
> Sergey
>
>    
>> Thanks,
>> Nirbhay
>>
>> On Friday 19 November 2010 03:25 PM, Sergey Vojtovich wrote:
>>      
>>> Hi Nirbhay,
>>>
>>> what is expected in the below example?
>>>
>>>        
>>>> One more use case :
>>>>
>>>> ./bin/mysql --one-database test
>>>>
>>>> mysql>   \R \d>
>>>> test>   drop database test;             # Query OK
>>>> (none)>   select 1;                          # Outputs 1
>>>> (none)>   create database test;      # Query OK
>>>> (none)>   select 1;                          # Outputs 1
>>>> (none)>use test;                           # Database changed
>>>> test>select 1;                               # Outputs 1
>>>>
>>>> In the above scenario, notice how prompt changes.
>>>>
>>>>          
>>>>>> Joro and Svoj expect queries to be accepted when one-databse is
>>>>>> "test" and
>>>>>> prompt says "test".
>>>>>> Nirbhay does not.
>>>>>>              
>>>> Now, in the above scenario, one-database is "test" but
>>>> prompt/current_db is not,
>>>> but we still have to keep executing the statements, as we started
>>>> with 'test' as
>>>> default database.
>>>>
>>>> Regards,
>>>> Nirbhay
>>>>
>>>> PS. Bug#54899 points to this scenario.
>>>>
>>>> -- 
>>>> MySQL Code Commits Mailing List
>>>> For list archives: http://lists.mysql.com/commits
>>>> To unsubscribe:    http://lists.mysql.com/commits?unsub=1
>>>>
>>>>          
>>
>> -- 
>> MySQL Code Commits Mailing List
>> For list archives: http://lists.mysql.com/commits
>> To unsubscribe:    http://lists.mysql.com/commits?unsub=1
>>
>>      
>