Menu

#1056 For editing long tables, allow SELECT

fixed
nobody
5
2013-06-11
2007-08-24
H. Hahn
No

If in a long table a few fields per record are to be edited manually, much scrolling is needed to find the field(s) in all those record, and too easily records may be overlooked.
This could be made much easier if a kind of SELECT were allowed to reduce the number of fields displayed in the edit screen. This way, we might SELECT only those fields that are to be editied as well as a few more fields needed to check which records must edited and which not.

Discussion

  • Marc Delisle

    Marc Delisle - 2007-09-07

    Logged In: YES
    user_id=210714
    Originator: NO

    IMO this should be done this way: start with the Search page, choose your columns to display, possibly limit the data with search conditions, then display. After, you could click some or all records and edit (currently the edit shows all columns again).

     
  • H. Hahn

    H. Hahn - 2007-09-07

    Logged In: YES
    user_id=1808692
    Originator: YES

    Dear mr. or ms. lem9,

    Thanks for your response.
    However, I am afraid I formulared my quention the wrong way. With "long tables" I did not intend to refer to tables with many records, but rather to records with many fields, i.e. tables with many columns.
    When I limit the select query to a few columns (only those to be changed and those needed to identify the records), then the form for editing the field contents still seems to show all fields. That is what I woud prefer to be changed: only those fields specified in the WHERE clause should be shown in the editing form.

     
  • Marc Delisle

    Marc Delisle - 2007-09-07

    Logged In: YES
    user_id=210714
    Originator: NO

    Yes I understood correctly your request, this is why I wrote about starting with the Search page and choosing your columns. phpMyAdmin's behavior works for the displayed results but does not work to edit those results, as you noted.

     
  • Marc Delisle

    Marc Delisle - 2008-01-08
    • status: open --> pending
     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539
    Originator: NO

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending --> closed
     
  • Michal Čihař

    Michal Čihař - 2013-06-11
    • Status: closed --> fixed