Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are essentially 3 ways to go:</p> <p><strong>Version 1: "Old school": PHP-Gtk+ and bcompiler</strong></p> <ul> <li>first, if you not have done so already, you need to separate your business logic from your presentation layer (HTML, templating engines, ...) and database layer</li> <li>then adapt your database layer, so that it can live with an alternative DB (local SQlite comes to mind) and perform synchronisation when online again</li> <li>Finally use PHP-Gtk+ to create a new UI and pack all this with bcompiler</li> </ul> <p><strong>Version 2: "Standard": Take your server with you</strong></p> <ul> <li>Look at Server2Go, WampOnCD and friends to create a "double clickable webserver" (Start at <a href="http://zwamp.sourceforge.net/" rel="noreferrer">Z-WAMP</a>)</li> <li>You still need to adapt your DB layer as in Version 1</li> </ul> <p><strong>Version 3: "Web 2.x": Move application from server to browser</strong></p> <ul> <li>Move your application logic from the server side (PHP) to the client side (JS)</li> <li>Make your server part (PHP) only a data access or sync layer</li> <li>Use the HTML5 offline features to replace your data access with local data if you are offline and to resync if online</li> </ul> <p><strong>Which one is best?</strong></p> <p>This depends on what you have and what you want. If most of your business logic is in PHP, then moving it into the browser might be prohibitingly expensive - be aware, that this also generates a whole new class of security nightmaares. I personally do not recommend <strong>porting</strong> this way, but I do recommend it for new apps, if the backing DB is not too big.</p> <p>If you chose to keep your PHP business logic, then the desicion between 1 and 2 is often a quiestion of how much UI does your app have - if it's only a few CRUD forms, 1. might be a good idea - it is definitly the most portable (in the sense of taking it with you). If not, go with 2.</p>
    singulars
    1. This table or related slice is empty.
    1. POhow to build a php mysql application that works offline
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USEugen Rieck
    1. USEugen Rieck
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POhow to build a php mysql application that works offline
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. This table or related slice is empty.
 

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