On Sun, Jun 19, 2011 at 8:58 PM, Ammar Yasir <
ammaryasir.88@gmail.com> wrote:
>
>
> On Sat, Jun 18, 2011 at 4:42 PM, Marc Delisle <
marc@infomarc.info> wrote:
>>
>> Le 2011-06-17 18:16, Ammar Yasir a écrit :
>> > On Fri, Jun 17, 2011 at 11:49 AM, Marc Delisle <
marc@infomarc.info>
>> > wrote:
>> >
>> >> Ammar,
>> >> it works well so far!
>> >>
>> >> Suggestions:
>> >>
>> >> - As the default data label, use the display field if it exists (from
>> >> libraries/relation.lib.php, PMA_getDisplayField() )
>> >>
>> >> - For the title, instead of "Scatter Plot", give some indications (how
>> >> to zoom, how to click, etc) or give a link to get such indications
>> >>
>> >> - Is it possible to enlarge the size of the working zone? ideally, to
>> >> drag it by one of its corners?
>> >>
>
> I used the jquery-ui plugin and implemented this.
>>
>> >
>> > :) I'll try and look into it.
>> >
>> >
>> >> - You seem to prefetch the whole table and I'm concerned about response
>> >> time and memory issues for big tables (try it with the payment table
>> >> and
>> >> no data restriction). When hovering over a dot, maybe fetch the rows
>> >> one
>> >> by one with Ajax? Or use Ajax if there are more than a certain number
>> >> of
>> >> rows.
>> >>
>> >
>> > I was also very much concerned about this. This happens even with the
>> > 'Display chart' functionality in the browse tab. I pre-fetch the table
>> > for
>> > making the initial plot and store the data row for each point. One
>> > solution
>> > can be like: Now I'm generating query like 'Select * from table' which
>> > I'll
>> > change to 'Select x,y from table' and then when hovering or clicking
>> > over
>> > the plot, I'll fetch the data row.
>>
>> Your solution of fetching just the needed columns will help, but we'll
>> need another safeguard for big tables. I'm thinking of a configurable
>> maximum of rows to fetch. Think of it, showing millions (or even
>> thousands) of dots won't make any sense.
>>
> So like in table browse mode we can generate the plot for 500/250 rows. Then
> if user wants we can replot with the next 500/250. Although I agree it will
> only complicate the plot and its hard to make sense from the plot.
> Or we can also ask the limit as input but I think the user might find it
> annoying or unnecessary.