GSoC (week 10)
1.solved the problem which was causing a crash for the optimized version.
2.modified some functions for renaming a column using alter table.
3.At first,the server crashed for queries like "select column_name from
table_name " if the column was present in the hash index. The probl
GSoC (week 9)
InnoDB
1. After modifying row_merge_tuple_cmp to compare actual fields for the
hash index, adding unique index through alter table was not working. It
was due to tuples that were inserted in the order of user defined fields
but for the hash index, they should have been inserted in
GSoC (week 8)
MyISAM
1.Finally solved a problem which was causing a server to crash in an update
query.Now the test results for update operation looks promising.
2. Changed the order of keys in MyIsam.Now the order of keys will be same
in sql layer and MyISAM.
3.modified check_definition.
4.ad
GSoC (week 7)
Hello everyone,
After implementing actual row comparison, there was a problem with
retrieving multiple clustered records with same hash value. The problem was
solved by putting search function of clustered record in the mini
transaction. The next thing I implemented in this week is
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 record. Currently trying to solve
the problem with multiple records with same hash va
GSoC (week 5)
Hello everyone,
Here is the list of things I have done in the 5th week of GSoC.
1.implemented unique key violation with a hash collision. (actual row
comparison is remaining ).
2.modified hash function for data types like varchar and binary data types.
3.fixed a bug which was ca
Hi,
Please commit and push these changes to your git branch I have not yet seen
them, in my opinion as this is only a working branch you can push often. I
still fail to see any test cases on InnoDB branch, do you have more than
one branch and if you have why ? Depending on extent of these changes
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
Hi, Shubham!
On Jun 14, Shubham Barai wrote:
> GSoC (week 3)
>
> Hello everyone,
>
> I worked on InnoDB for this whole week. For each index of type
> DICT_UNIQUE_HASH, an extra column is added after user defined columns and
> before system defined columns.I have created new prtype(precise type)
GSoC (week 3)
Hello everyone,
I worked on InnoDB for this whole week. For each index of type
DICT_UNIQUE_HASH, an extra column is added after user defined columns and
before system defined columns.I have created new prtype(precise type) for
hash based columns.I have resolved some of the issues af
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 approach for this
with the help of my mentor.
One of the other issues that I had to deal with was compatibility issue of
key definitions between .fr
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,
12 matches
Mail list logo
