{
    "href": "/post/2004/11/02/a-development-infrastructure-for-php-sitepoint-php-blog/",
    "relId": "2004/11/02/a-development-infrastructure-for-php-sitepoint-php-blog",
    "title": "A cousin, of sorts, to DB_Table?",
    "author": "pmjones",
    "markup": "html",
    "tags": [
        {
            "href": "/tag/php/",
            "relId": "php",
            "title": "PHP",
            "author": null,
            "created": null,
            "updated": [],
            "markup": "markdown"
        }
    ],
    "created": "2004-11-02 18:22:24 UTC",
    "updated": [
        "2004-11-02 18:22:24 UTC"
    ],
    "html": "<p>It seems I am not alone in thinking it is wise to embed database table column information in the PHP class that will interface with that table.  Harry Fuecks, in his blog entry titled <a href=\"http://www.sitepoint.com/blog-post-view.php?id=206854\">A Development Infrastructure for PHP</a>, points to work by <a href=\"http://www.tonymarston.net/php-mysql/infrastructure.html\">Tony Marston</a>.</p>\n<p>Check out Tony's notes about his <a href=\"http://www.tonymarston.net/php-mysql/model-view-controller.html#%24fieldspec\">business class field properties</a> and compare with <a href=\"http://wiki.ciaweb.net/yawiki/index.php?area=DB_Table&amp;page=GettingStartedSchema\">the DB_Table schema setup</a> documentation.  They are obviously very similar, at least in example and documentation.  The both do automated validation as well, and have \"hints\" for form-building embedded in the class.</p>\n<p>Nice to know someone is on the same path as me (although Tony is obviously **much** further ahead :-).</p>\n"
}