Hi,
Deven has done nice work on the print view[0] pull request but we've hit a bit of a grey area with regards to what to do with a view count. In the database structure page, in the standard "screen-based interface" we provide an approximate row count for a view and the user can click on the row count to get an exact number.
With print view, we could handle this in a couple of ways, each of which has a tradeoff. I think these are the two that I find most appealing.
1) We could only provide an approximate count. This is programmatically easiest and provides instant results, but might frustrate some users.
2) We could provide an exact count, computed when the user presses the print button. We should probably display a dialog during the counting such as "Getting an exact count for views, the print dialog will appear once the MySQL server is done counting." A shortcoming is that the count would only be triggered by the "Print View" link, not when they use their print function of the browser. Users with many complex views may not care about an exact count and may want a quick print dialog, so we might need to provide yet another configuration directive about this.
How does the rest of the team feel about this?
On Sun, May 31, 2015 at 8:26 PM, Isaac Bennetch bennetch@gmail.com wrote:
Hi,
Deven has done nice work on the print view[0] pull request but we've hit a bit of a grey area with regards to what to do with a view count. In the database structure page, in the standard "screen-based interface" we provide an approximate row count for a view and the user can click on the row count to get an exact number.
With print view, we could handle this in a couple of ways, each of which has a tradeoff. I think these are the two that I find most appealing.
- We could only provide an approximate count. This is programmatically
easiest and provides instant results, but might frustrate some users.
- We could provide an exact count, computed when the user presses the
print button. We should probably display a dialog during the counting such as "Getting an exact count for views, the print dialog will appear once the MySQL server is done counting." A shortcoming is that the count would only be triggered by the "Print View" link, not when they use their print function of the browser. Users with many complex views may not care about an exact count and may want a quick print dialog, so we might need to provide yet another configuration directive about this.
How does the rest of the team feel about this?
0 - https://github.com/phpmyadmin/phpmyadmin/pull/1708
I am fine with the first option. If a user wants to get the real counts,
he/she can click on the links and then go for the print option, right? Apart from this, may be we need a way to fetch real counts for all the views at once (for example, making total count clickable)
On 5/31/15 11:09 AM, Madhura Jayaratne wrote:
On Sun, May 31, 2015 at 8:26 PM, Isaac Bennetch <bennetch@gmail.com mailto:bennetch@gmail.com> wrote:
Hi, Deven has done nice work on the print view[0] pull request but we've hit a bit of a grey area with regards to what to do with a view count. In the database structure page, in the standard "screen-based interface" we provide an approximate row count for a view and the user can click on the row count to get an exact number. With print view, we could handle this in a couple of ways, each of which has a tradeoff. I think these are the two that I find most appealing. 1) We could only provide an approximate count. This is programmatically easiest and provides instant results, but might frustrate some users. 2) We could provide an exact count, computed when the user presses the print button. We should probably display a dialog during the counting such as "Getting an exact count for views, the print dialog will appear once the MySQL server is done counting." A shortcoming is that the count would only be triggered by the "Print View" link, not when they use their print function of the browser. Users with many complex views may not care about an exact count and may want a quick print dialog, so we might need to provide yet another configuration directive about this. How does the rest of the team feel about this? 0 - https://github.com/phpmyadmin/phpmyadmin/pull/1708I am fine with the first option. If a user wants to get the real counts, he/she can click on the links and then go for the print option, right?
That's a good point, then we're not making the user wait and if they want an exact count, they can get it themselves.
Apart from this, may be we need a way to fetch real counts for all the views at once (for example, making total count clickable)
This is an interesting suggestion.
Thanks for the feedback!
-- Thanks and Regards,
Madhura Jayaratne
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
On Sun, May 31, 2015 at 8:39 PM, Madhura Jayaratne madhura.cj@gmail.com wrote:
On Sun, May 31, 2015 at 8:26 PM, Isaac Bennetch bennetch@gmail.com wrote:
Hi,
Deven has done nice work on the print view[0] pull request but we've hit a bit of a grey area with regards to what to do with a view count. In the database structure page, in the standard "screen-based interface" we provide an approximate row count for a view and the user can click on the row count to get an exact number.
With print view, we could handle this in a couple of ways, each of which has a tradeoff. I think these are the two that I find most appealing.
- We could only provide an approximate count. This is programmatically
easiest and provides instant results, but might frustrate some users.
- We could provide an exact count, computed when the user presses the
print button. We should probably display a dialog during the counting such as "Getting an exact count for views, the print dialog will appear once the MySQL server is done counting." A shortcoming is that the count would only be triggered by the "Print View" link, not when they use their print function of the browser. Users with many complex views may not care about an exact count and may want a quick print dialog, so we might need to provide yet another configuration directive about this.
How does the rest of the team feel about this?
0 - https://github.com/phpmyadmin/phpmyadmin/pull/1708
I am fine with the first option. If a user wants to get the real counts,
he/she can click on the links and then go for the print option, right? Apart from this, may be we need a way to fetch real counts for all the views at once (for example, making total count clickable)
The feature already exists in some inconsistent way. The 'Total Rows' in 'information_schema' is clickable and gets all the real row counts. But in db like 'sakila', which has both tables and views, it is not clickable.
I created a new feature request related to this : [0] and submitted a PR : [1]
[0] : https://sourceforge.net/p/phpmyadmin/feature-requests/1676/ [1] : https://github.com/phpmyadmin/phpmyadmin/pull/1709%E2%80%8B
-- Thanks and Regards,
Madhura Jayaratne
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Le 2015-05-31 10:56, Isaac Bennetch a écrit :
Hi,
Deven has done nice work on the print view[0] pull request but we've hit a bit of a grey area with regards to what to do with a view count. In the database structure page, in the standard "screen-based interface" we provide an approximate row count for a view and the user can click on the row count to get an exact number.
With print view, we could handle this in a couple of ways, each of which has a tradeoff. I think these are the two that I find most appealing.
- We could only provide an approximate count. This is programmatically
easiest and provides instant results, but might frustrate some users.
- We could provide an exact count, computed when the user presses the
print button. We should probably display a dialog during the counting such as "Getting an exact count for views, the print dialog will appear once the MySQL server is done counting." A shortcoming is that the count would only be triggered by the "Print View" link, not when they use their print function of the browser. Users with many complex views may not care about an exact count and may want a quick print dialog, so we might need to provide yet another configuration directive about this.
How does the rest of the team feel about this?
3. We could provide no row count at all in print view.
-
Deven Bansod -
Isaac Bennetch -
Madhura Jayaratne -
Marc Delisle