Databases
StackOverflow2013
Postsdbo
POUse common functions and views for web database applications
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUse common functions and views for web database applications
    primarykey
    data
    text
    <p>I have a design discussion with a collegue.</p> <p>We are implementing a PHP MySQL database application. In the first instance we have written the Insert Get Update Delete, SelectAll and Search functions for a particular table, writting the table and fieldnames in the code, with several php files, one for the object class, one to draw the HTML table for that table, one for editing a row of that table, one containing the above functions, etc.</p> <p>The disagreement comes as I have now written generic functions that read/write from the database and draw the HTML taking the table name as a parameter, letting these functions discovers the fieldnames from the database or class. So now that code can be used for any table, with any fields without having to manually go in change each function that needs alteration. I understand there will be cases where more table specific functionality is needed, and this I think that should be done as requirements arise, integrating common parts where possible.</p> <p>My collegue on the other hand is adamant we should keep a set of files separate for each table, i.e. around 5 php files for each table. The read/write functions written differently in each case, with the need for any changes required for all tables to be affecting 5 x number of tables amount of times. </p> <p>I can certainly say there will be more than main 15 tables in the database that will at least need basic funcionality.</p> <p>What approach do you think is most appropriate?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKMån
    1. USalex
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUse common functions and views for web database applications
      1. USLaxman13
      1. VTFavorite
    2. VO
      singulars
      1. POUse common functions and views for web database applications
      1. USalex
      1. VTFavorite
    1. CO*Why* is your colleague adamant about keeping a separate set of files for each table?
      singulars
      1. POUse common functions and views for web database applications
      1. USMike Sherrill 'Cat Recall'
    2. COHe says that data access and visualization will be sufficiently different for each table and use case that passing as paramaters variables such as tablename, classname or fieldsnames, rather than just writing those explicity in the SQL statement, will ulimately require too many if/switch constructs to manage, and that keeping a different set of code for each table, even for such things as "SELECT * FROM Table" and draw an HTML table is a easier to maintain in the long run.
      singulars
      1. POUse common functions and views for web database applications
      1. USalex
    3. CO@alex: Is he right? What does he know that you don't? (My general rule for dealing with adamant designers and programmers is to consider myself ignorant of their understanding until I understand their ignorance.)
      singulars
      1. POUse common functions and views for web database applications
      1. USMike Sherrill 'Cat Recall'
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload