ore actual key values ,it is not possible to get the
required row by scanning hash index.So I modified write_record to use
sequential scan if the duplicate key error is in hash index.
Regards,
Shubham
On 28 July 2016 at 00:26, Shubham Barai wrote:
> GSoC (week 9)
>
> InnoDB
>
> 1
row0merge.cc to compare
externally stored columns for the hash index.
So far insert, update and delete works for almost all cases. In alter
table, rename column is remaining.
Regards,
Shubham
On 21 July 2016 at 00:00, Shubham Barai wrote:
> GSoC (week 8)
>
> MyISAM
>
> 1.Finally solved
.added tests for alter table and update operation.
current branch for MyIsam : Myisam
InnoDB
1.Fixed a bug in update operation.
2.added tests for alter table
current branch for Innodb : temp
On 13 July 2016 at 13:47, Shubham Barai wrote:
> GSoC (week 7)
>
> Hello everyone,
x.
On 5 July 2016 at 00:33, Shubham Barai wrote:
> GSoC (week 6)
>
> Hello everyone,
>
> 1. defined some new functions to get the clustered record from secondary
> index record and extract its key value to compare with the secondary index
> key.It works for single clustered reco
all of the key parts are present in
search key.
current branch for InnoDB : temp
On 27 June 2016 at 19:23, Shubham Barai wrote:
> GSoC (week 5)
>
>
> Hello everyone,
>
> Here is the list of things I have done in the 5th week of GSoC.
>
> 1.implemented unique key violati
causing a server to crash for complex unique keys.
4.added support to allow any number of nulls which will not cause any
unique key violation.
5.added test cases for above features.
On 22 June 2016 at 16:36, Shubham Barai wrote:
> Hi,
>
> can we discuss on IRC first?
>
>
>
GSoC (week 4)
Hello everyone,
After working on create table operation,next thing I had to work on was
insert operations.So I explored some of the functions like
row_ins_scan_index_for_duplicates, btr_pcur_get_rec to get clear
understanding about how to implement duplicate search on hash index.
Th
and row0mysql.cc to support a new
index type.
Regards,
Shubham
On 6 June 2016 at 22:57, Shubham Barai wrote:
> GSoC (week 2)
>
> Hello everyone,
>
> Finally, I solved the issue with a mismatch of a key number
> between sql layer and MyISAM file.I also found a simpler approa
03:32, Sergei Golubchik wrote:
> Hi, Shubham!
>
> Good, thanks!
>
> On May 31, Shubham Barai wrote:
> > GSoC (week 1)
> >
> > Hello everyone,
> >
> > After developing a prototype for MyISAM ,there were some issues to be
> > resolved. One of the is
GSoC (week 1)
Hello everyone,
After developing a prototype for MyISAM ,there were some issues to be
resolved. One of the issues is related to error regarding a duplicate
entry. So if there is a duplicate entry for a particular key in a row, it
generates an error for another key.
After debugging,
Hi Sergei,
I was trying to debug mysqld using gdb.I used full backtrace option but I
didn't get the stack trace for queries that I executed. Could you please
help me out with this?
Regards,
Shubham
On 27 April 2016 at 16:57, Sergei Golubchik wrote:
> Hi, Shubham!
>
> On Apr 26,
Hi Sergei,
Here is the link to new repository
https://github.com/shubhambaraiss/MariaDB.git
As you said, I pushed changes with git.
Regards,
Shubham
On 24 April 2016 at 14:28, Sergei Golubchik wrote:
> Hi, Shubham!
>
> On Apr 24, Shubham Barai wrote:
> > Hi Sergei,
>
bchik wrote:
> Hi, Shubham!
>
> On Apr 24, Shubham Barai wrote:
> > Hi Sergei,
> >
> > I have created github repository with a new branch for my prototype.
>
> Great, what's the url?
>
> btw, please, use "Reply to all", so that the whole list co
, Shubham Barai wrote:
> Hello Jan,
>
> Thanks for the kind response and for giving the details of
> implementation. I am going to explore InnoDB data dictionary before the
> official coding period starts.
>
> Thanks,
> Shubham
>
> On 24 March 2016 at 01:47, Se
Hello Jan,
Thanks for the kind response and for giving the details of
implementation. I am going to explore InnoDB data dictionary before the
official coding period starts.
Thanks,
Shubham
On 24 March 2016 at 01:47, Sergei Golubchik wrote:
> Hi, Jan!
>
> On Mar 23, Jan Lindström wrote
are actual values.
This is my initial approach for implementing long unique constraints in
InnoDB.
Do you think this approach will work?
I would really appreciate your suggestions.
Thanks,
Shubham
On 22 March 2016 at 20:58, Shubham Barai wrote:
> Hello Sergei,
>
> I und
Hello Sergei,
I understood most of the internals of long unique constraints in
MyISAM. I am still going through the code in InnoDB. I will soon reply to
you.
Thanks,
Shubham
On 21 March 2016 at 16:37, Sergei Golubchik wrote:
> Hi, Shubham!
>
> On Mar 21, Shubham Ba
m!
>
> On Mar 20, Shubham Barai wrote:
> > Hi Sergei,
> >
> > As I told you, I was working on prototype just for blobs. I was
> > having some issue with key definition between MariaDB .frm file and
> > information in the MyISAM storage engine. I have solve
3 | b2 | A |
0 |5 | NULL | YES | BTREE | | |
+++--+--+-+---+-
+--++--++-+---+
3 rows in set (0.00 sec)
Any suggestions would be helpful.
Thanks,
Shubham
On 20 March 2016 at 11:10, Shubham Barai wrote:
> Hi Sergei,
&
ubham
On 19 March 2016 at 14:22, Shubham Barai wrote:
> Hello Sergei,
>
> As you suggested, I tried to develop a prototype just for
> blobs.
> So far it is working fine but I am still verifying it for different
> cases.
> I will provide you the link to my
wrote:
> Hi, Shubham!
>
> On Mar 16, Shubham Barai wrote:
> > Hello, Sergie!
> > I tried to explore the source code from
> > mi_create.c,ha_myisam.cc,sql/sql_table.cc,include/myisam.h,.and some
> other
> > files.
> > The main task is to create MI_UNIQUEDEF
nfo struct in
mysql_prepare_create_table if any one of the key_part consists of blob
field without prefix length.
Later we can check the flag in table2myisam to see if we want to create
MI_KEYDEF or MI_UNIQUEDEF.
Thanks,
Shubham.
On 5 March 2016 at 03:52, Sergei Golubchik wrote:
> Hi, Shubham!
>
> On
Hello everyone,
I am Shubham Barai, a 3rd-year undergraduate student in
computer science at Maharashtra Institute of technology, Pune, India.
I am interested in the project "Unique indexes for blobs".I have read the
description of the project given on the
23 matches
Mail list logo
