Gsoc weekly statuts Report

Hi all,

Now only a week is left for Gsoc ,it has been a really good learning experience,
now as the coding period ends , it’s time to start working on documentation and
continue with bug fixes

coming to the status report last week finally i completed from and having clauses .
and now we have auto joins support on visual builder
i figured out a few bugs , now this week will be fixing those and do a thorough testing.
and complete the documentation .

weekely status report

Hi all,

Last week i completed the from clause which was only thing left in query building,
now i am testing it on my machine, there are few issues with automatic joins which i will fix

Plans for next week are resolve join issues testing and fixing bugs, improve styling.

Gsoc status Report

Hi all,

i had decided that by 25th i will complete the query building, but i got sick in between
and it took a couple of days to recover  .
Now i am all fit and fine  and will try to complete the query building by the end of this week.
i have already completed select clause,where clause,order by and group by clauses.
main part remaining is FROM clause and generating LEFT JOINS.
I have figured out the logic for that and will implement it by the end of this week.

also while implementing order by and  group by i felt few changes are needed in design
so am planning to  add Ascending and Descending button for ORDER BY
and include a HAVING clause with GROUP By.

Weekly status report -Gsoc

Hi all,

Finally the ‘Query Building’ part of visual builder has started !!
Select options with rename and aggregate operator part of query building is complete .

To store select options i used a select_field[] array, some changes were made to implement select * option, query for rename and aggregate operator is done.
A Query window is also created which shows the query built.

Next week i am planning to complete From part of builder and start working on where.

Weekly status Report-Gsoc

Hi all,

Last week i travelled a lot, made a round trip to delhi and then to bangalore, so was not able to do much though i almost completed the history tab(have to remove a few bugs), now have to test it on other browsers, currently i have tested only on firefox v 3.6.6 .

Last week tasks done

• improved the styling of history tab
• Added new delete button .
• Added edit option,for where,rename and aggregate to change these options.
• Added detail button in history tab.

Tasks for next week

• Check history tab on other browsers.
• build a data-structure to store selected columns.
• build a query window.
• start on query building

Weekly status report

History tab is taking more time than what i planned , still i have to improve styling and add few features.

while implementing i realized that clubbing  all object with same table name together will be a good option ,as user can easily see what all conditions are  imposed on a particular table.

I have made a history_array[] to store all the history objects(where,rename,aggregate,groupby,orderby).
so now we will have all the information needed for query building in this data structure.

for the next week i am planing to complete history tab, improve the styling and  add edit and remove features

Status report Gsoc week 3

last week i started working on history tab

Tasks Done

• J-Query : was thinking to use j-query for implementation of history panel, but i have no previous experience so learned the basics.
• implemented a OOP model for history panel.

Tasks For next week

start work on display of history with various options (delete,edit etc)

Weekly status repot Gsoc -week2

Here is my status report for last week (2nd week).

Tasks Completed

• Adding Select Option with each columns and implemented select all check-box.
• Refactor the code in pmd_general to include new features and making a link in query tab to redirect  to visual builder.
• Options : made a few changes in design while implementing, i felt there is no need to show an extra window showing various options available better will be if we show one window with all operations.

Things which i couldn’t complete is designing icon for option and i have used  (exec.png)  temporarily.

Task for Next week

History tab, start building history tab and its features.

Weekly status report Gsoc -week 1

First week of Gsoc ended and here is my status report.

Task Completed

• Forked my Git repo: it was my first encounter with git, introduced myself  to git and played with git commands. My fork’s urls
  http://repo.or.cz/w/phpmyadmin/ankitg.git .
• Design: few changes in the design were made,history panel of “visual builder” was modified to incorporate self join operation.
• I saw the working of pmd_general and move.js ,was figuring refactoring methods.

Task scheduled for next week

• refactor functions in pmd_general and move_js to incorporate new fearures.
• Add check-boxes and option button with each entity in designer.
• implement the design of Where,aggregate,rename,order by and group by windows.
• Start building history panel.

Few Changes

Now Gsoc coding period starts,here i suggest  few changes in the Design of Visual Query builder.

History

History  will have four main part Object ,Detail,And/Or indicator and Delete

1) Object : This column is for support of self Join operations,in this all operations(where,having,etc..) which belong to same object of table will be stacked together.In the Object column we will have a Drop down-list containing all Object for that particular table and option to add new object.  By default when a new operation is added it will have the same value as that of last used object value for that table.

2) Detail : Will contain detail information about the operation.

3) And/Or Indicator : This will have two options(Green=And,Red=Or) which can be change from on/and by clicking on the and/or(Indicator will change colour on mouse click event), default Colour will be Green(And).

4) Delete : To delete a particular operation tab.

Join Relation

To support self Join operation,select table , select objects and specify details for where condition.

This will add a new entry in History.

example query : to select the id-no’s ,where comp-code of courses having instructorIncharge as “mark” is less than comp-code of courses having Units =3

Select idNo from component ,course c1,course c2 where c2.instructorIncharge=”mark” and c1.unit=3 and c1.compcode>c2.compcodeFor above query we will check idNo in component table,then will add c1 and c2 objects and finally add relation for c1 and c2.by selecting table name as course,object1 as c1 and object2 as c2 and then selecting attribute as Compcode and finally selecting “>” relationship.