[Maria-developers] GSoC 2016 CONC-125
Hi everyone, I am Christian Massey a computer science student at York University and I wish to work on Providing import and export functions for popular data formats like JSON, XML , PHP, ... for Connector/C and MariaDB Server. I have been inspecting the code to understand how the dynamic column packed string is encoded and I see kind on big endian encoding( Correct me if I am wrong please). Also I see that the old format already work like arrays and it uses 3 bits for encoding type which is the main reason why not all types in the enum are supported in this old format. DBUG_ASSERT(((type - 1) & (~7)) == 0); /* fit in 3 bits */ (Again please correct me if I am wrong. The encoding is not easy to understand) My Question is do we need to create a completely new type to support arrays or do we change the old format which already work like arrays in a way but lacks support for some types(I don't know which of the enums yet). Please, I wish to write a proposal for this project and hope to discuss more with mentors for more clarification on how we are going to implement this as it seems to be a very important if not the most critical part of this project. Cheers, Kris.
Hi, Christian! On 06.03.2016 12:23, Christian Massey wrote:
Hi everyone,
I am Christian Massey a computer science student at York University and I wish to work on Providing import and export functions for popular data formats like JSON, XML , PHP, ... for Connector/C and MariaDB Server. I have been inspecting the code to understand how the dynamic column packed string is encoded and I see kind on big endian encoding( Correct me if I am wrong please).
Also I see that the old format already work like arrays and it uses 3 bits for encoding type which is the main reason why not all types in the enum are supported in this old format.
DBUG_ASSERT(((type - 1) & (~7)) == 0); /* fit in 3 bits */
(Again please correct me if I am wrong. The encoding is not easy to understand)
You are right.
My Question is do we need to create a completely new type to support arrays or do we change the old format which already work like arrays in a way but lacks support for some types(I don't know which of the enums yet).
How it is done internally not so important. But "externally" it should be new type because: 1) we should read old types 2) we can't use old "as is" because it lack types But "internally" code can be of course reused.
Please, I wish to write a proposal for this project and hope to discuss more with mentors for more clarification on how we are going to implement this as it seems to be a very important if not the most critical part of this project.
Cheers, Kris.
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
Hi Oleksandr, MariaDB Mentors, I have submitted a draft proposal for this project on the summer of code website. Please kindly review it and leave comments so I can make any necessary corrections. Cheers, Christian 2016-03-06 15:53 GMT+01:00 Oleksandr Byelkin <sanja@montyprogram.com>:
Hi, Christian!
On 06.03.2016 12:23, Christian Massey wrote:
Hi everyone,
I am Christian Massey a computer science student at York University and I wish to work on Providing import and export functions for popular data formats like JSON, XML , PHP, ... for Connector/C and MariaDB Server. I have been inspecting the code to understand how the dynamic column packed string is encoded and I see kind on big endian encoding( Correct me if I am wrong please).
Also I see that the old format already work like arrays and it uses 3 bits for encoding type which is the main reason why not all types in the enum are supported in this old format.
DBUG_ASSERT(((type - 1) & (~7)) == 0); /* fit in 3 bits */
(Again please correct me if I am wrong. The encoding is not easy to understand)
You are right.
My Question is do we need to create a completely new type to support arrays or do we change the old format which already work like arrays in a way but lacks support for some types(I don't know which of the enums yet).
How it is done internally not so important. But "externally" it should be new type because: 1) we should read old types 2) we can't use old "as is" because it lack types
But "internally" code can be of course reused.
Please, I wish to write a proposal for this project and hope to discuss more with mentors for more clarification on how we are going to implement this as it seems to be a very important if not the most critical part of this project.
Cheers, Kris.
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
participants (2)
-
Christian Massey -
Oleksandr Byelkin