I agree with BobRay. If you’re going to be doing your own CRUD (create, read, update, delete) in the database, what’s the point of using modx?
modx gives you the ability to do the Create,Update,Delete via TVs and the manager. Read via [*content*] or Ditto.
If you need a custom table (which might be good), I would still let modx do all of the CRUD and use Quid to save the info into another table. You can set these pages as uncacheable.
Wouldnt it make more sense to use modx’ powerful manager interface for CRUD and Ditto for views, and optimize the caching mechanism rather than building your own custom-db tools?
modx advantages
- easily create new fields (via TVs)
- can aggregate rows of data (via Ditto) and its templateable
- create RSS of the library (via Ditto)
- can easily search all rows (via ajaxsearch)
- user permissions (either per document or per tv field)
why would you want to have to do this from scratch unless you want to create some db superclass to handle rows as objects, etc? If you’re going to recreate all of this, you might as well use CodeIgniter, Symfony, or another ’library app’ like BobRay pointed to.
Quid is here:
http://modxcms.com/Quid-2305.html
- Quit automatically updates an external table with modx content, TVs and document contents.