Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Since paging isn't an option...</p> <p>You're right that it doesn't matter what technology you're using - more curiosity than anything on my part. Also, I'm not familiar with PHP so take my ideas as abstract here please. Have you tried/considered the following (I created a fiddle to demonstrate the graphical portion of this <a href="http://jsfiddle.net/ninja1/ynuDV/" rel="nofollow">http://jsfiddle.net/ninja1/ynuDV/</a>):</p> <ul> <li>Use CSS "table" to define that the display for any/all "tables" in that given page use <code>display:inline-block;</code></li> <li>Render first table without any nesting. Use a button or whatever control you wish to have a lever/key/rowId/userId whatever you have that would reflect your selection.</li> <li>You'd then intercept this control's action, if a button - then whenever the button is clicked it would then call a method to create the second table dynamically and programmatically based upon the selection from table1.</li> <li>Once table 2 has been rendered with input from table1, the same rule would apply to table2. Use a control again and capture/leverages the selection from table2 to then end up being the input for table3 to be created programmatically.</li> </ul> <p>As you can see by the fiddle I've attached here; try resizing the pane by grabbing the center divider and moving it left/right. You'll notice that the tables line-up next to each other should the display size allow them to.</p> <p>Hope this helps :) let me know.</p> <hr> <p>I think the best approach here is to make paging available to the table.</p> <p>Additionally, you could allow the user to set the size of the page that is rendered - therefore allowing them to optimize for their best performance. So you would have a textbox underneath the table that the user can edit and is pre-populated with your initial decision of let's say 20 records per page.</p> <p>Lastly, make sure to implement the SQL query/stored proc with a page-size and page number parameters so the database does the logic and only returns the dataset required. Consider something like this <a href="http://blog.sqlauthority.com/tag/sql-paging/" rel="nofollow">http://blog.sqlauthority.com/tag/sql-paging/</a></p>
    singulars
    1. This table or related slice is empty.
    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. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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