Hello Sergei!
Weekly Report for 9 week of gsoc

Unique Long 

1. Changed mysql_prepare_create function as suggested by you , now addition of hash column will not be added in function start.
2. Sorted out problem of full_hidden detection now it is detected as soon as it is found.

Where Optimization
1. In case of unique(a) if hash collides then it fetches the next record and compares it and so on.
2. Now unique(a,b,c ..) also works and also in case of hash collusion  it fetches the next record and compares it and so on.

Please review branch https://github.com/SachinSetiya/server/tree/unique_index_where
The only problem i have is explain query fails , trying to solve it let you know if something happens.

On Mon, Jul 25, 2016 at 1:34 AM, Sachin Setia <sachinsetia1001@gmail.com> wrote:
Actually  i find that my_strnncoll  wil work :) 

On Mon, Jul 25, 2016 at 1:17 AM, Sachin Setia <sachinsetia1001@gmail.com> wrote:
Hello Sergei,
I am getting one problem related to my_strcasecmp() function currently this function does not allow 
string comparison upto length l, is there any functon which can do comparison upto length l, or should i 
write mine.

On Fri, Jul 22, 2016 at 9:56 PM, Sachin Setia <sachinsetia1001@gmail.com> wrote:
Hello Sergei,
I have one problem my where optimization works for  query like
select * from t1 where abc=1;

but in query like 
select * from t1 where abc=(select xyz from t2 where xyz=1);
does not work because in these query the charset is different from what used in 
t1 for inserting data and hence generation different hash for same data
how i solve this problem. 

On Tue, Jul 19, 2016 at 5:52 PM, Sachin Setia <sachinsetia1001@gmail.com> wrote:

Just give me 3 days after you can review. yes I already merged with 10.2.1 days ago.  

On Jul 19, 2016 17:28, "Sergei Golubchik" <serg@mariadb.org> wrote:
Hi, Sachin!

On Jul 19, Sachin Setia wrote:
> Weekly Report for 8 week of gsoc
> 1 Changed the key flags as suggested by you.


> 2 Now update will use only one buffer as suggested by you but there was one
> problem some time offset can be
> negative so i changed the field cmp_offset parameter from uint to long


> 3 Still working on coding conventions.
> 4 I have made prototype for optimizing where for keys like unique(a) , it
> is on branch
> https://github.com/SachinSetiya/server/tree/unique_index_where
> Currently I am working on muliple keys like unique(a,b,c) i think this
> should take 2-3 days  and edits suggested by you.

sounds good.
did you merge with 10.2.1?

tell me when you'd want me to do another review.

Chief Architect MariaDB
and security@mariadb.org