1. <label id="w2g2v"><ruby id="w2g2v"></ruby></label>

        <output id="w2g2v"></output>
        <blockquote id="w2g2v"><ruby id="w2g2v"></ruby></blockquote>
        Previously on the blog
        RSS feed
        1. Using POG with Flex
        2. Optimizing your web application
        3. Regenerating large objects
        4. PHP4 or PHP5
        5. New and Improved
        6. Evolution of a cube
        7. POG Museum
        8. POG 3.0 alpha
        9. Initial Performance results Part 2
        10. Initial performance results
        11. Proposal: POG 3.0 object model
        12. Suggest a feature
        13. A new year, A new POG release
        14. Many-Many relations
        15. POG 2.5 Released
        16. POG 2.5 beta
        17. Automatic table alignment
        18. New version: 2.1.2 released
        19. RSS should work well now
        20. RSS feed glitches
        21. What's new in 2.1.0
        22. PHP Objects 2.1.0 (preview)
        23. PHP Object relations FAQ
        24. PHP Object Relations
        25. Searching base64 encoded text
        26. How to debug POG-generated objects
        27. POG UI Tips
        28. Featuring Of Interest links
        29. PHP CRUD
        30. POG 2.0.1: A better code generator
        31. A look at the POG SOAP API
        32. POG 2.0.0 released
        33. Coming soon: Generate parent-child objects
        34. Generated abstraction v/s dynamic abstraction
        35. Zend Framework preview
        36. Coming soon: Generate Objects through SOAP
        37. Easily save images and files to a database
        38. PHP, Paypal & POG
        39. Five advanced Code Generator tips
        40. PHP Pagination using generated objects
        41. PHP Code Generator benchmarks
        42. Representing database objects using an AJAX Tree interface
        43. Using SETUP in a production environment
        44. Description of the generated object package
        45. Introducing PHP Object Generator version 1.6
        46. Using AJAX and PHP Object Generator
        47. When to use Object->SaveNew()
        48. Generating PHP objects in 2006
        49. Happy Holidays
        50. A short video of the POG Setup process
        51. A sneak peek at POG 1.6
        52. POG Tip: Field limits
        53. Previous versions.
        54. Searching the blog and tutorials sections
        55. Generating code with "Other" SQL data types
        56. Five general POG tips
        57. POG source code locations
        58. Microsoft SQL 2005 Express Edition
        59. Impatiently awaiting PHP 5.1 and PDO
        60. Php Object Generator goes open source
        61. POG generates PDO compatible code
        62. Oracle to offer free database
        63. POG Google group
        64. Database Wrappers and POG
        65. Revisions
        66. The generator blog
        67. An explanation of the 'Escape' function.
        68. Mirror, mirror
        69. Using POG to solve real world problems
        70. A php object-relational database tool
        71. A simple and flexible Object Oriented approach to PHP


        Want more Php Object Generator?
        Back to the Code Generator
        The POG Google group
        The POG tutorials/code samples
        The POG mirror site




        PHP CRUD

        written 4809 days ago

        As most of you know by now, CRUD stands for Create, Retrieve, Update, Delete and is one of the ‘philosophies’ behind POG, enabling PHP developers to generate the database abstraction required to perform these 4 atomic database operations (and more).

        Now, POG is far from being the only solution when you want to use CRUD to ease your database application development. Here are some alternatives:

        Using Stored Procedures
        This approach is usually taken when you want to isolate database development from application development as much as possible. Teams are then usually split into a ‘database team’ and an ‘application team’. The database team is responsible for developing stored procedures that perform CRUD operations and the application team is responsible to create the stored procedure calls from within the application. Apart from achieving isolation, there aren’t any outstanding advantages to this method if it involves only CRUD operations. (and it actually defeats the purpose of CRUD in the first place). However, if you application relies on complex business rules and lots of tables and data transformation, stored procedures might be the way to go.

        Dynamic CRUD libraries
        There are a few dynamic CRUD libraries out there: PHP CRUD, Active Record (Ruby), MySQL table wrappers etc. These libraries analyze your tables and create dynamic, virtual ‘php objects’ that can be saved, deleted, created and updated. The code overhead is usually less than if you were using generated objects your entire application is then highly coupled with you data abstraction library. The CRUD operations are also slower than if you use code generation to create static objects that match your database.

        PHP Frameworks
        Another alternative is to download and learn one of the numerous PHP application development frameworks available out there. Frameworks usually provide a high level API to commonly performed coding tasks, database abstraction or CRUD usually being one of them. The Zend framework is an example of such frameworks. Frameworks are usually useful if you’re building large web applications and want to take advantage of a variety of different abstractions provided by the framework. So, frameworks are good if you take advantage of a lot of the components they provide, but too much if you’re only looking for database abstraction.

        Back to Code Generation
        Code generation, is, I believe, still very-much underrated as an option for tackling database abstraction and CRUD. I’ve had experiences with different database application development strategies over the years, as well as different programming styles ranging from eXtreme programming to formal, documentation-driven development. From these different experiences, I can honestly say that code-generation is the one I find the most efficient and productive. Example: One team I worked with consisted of 2 sub teams: The database guys and the application guys. Once every 2-3 months, the database team would make some schema changes to accommodate for new feature requests. At first, the application team used a dynamic object database library which worked well most of the time but because it was so tightly coupled with the application code, would break different parts of the application when it couldn’t handle the schema change, resulting in many hours of trying to figure out why the abstraction library was messing up. The application team then decided to spend some time to implement a simple code generator, which would generate once and for all the required objects and never have to think of it again until the next set of schema changes. They also used code generation to generate constant strings for table names, column names etc that are used by stored procedure calls, instead of keeping everything dynamic.

        Keeping everything dynamic might seem cool at first sight, but it almost ends up with the developers wasting many hours debugging a library that they didn’t even write in the first place. The reason why I keep advocating for new developers to try POG and give us your opinion is because POG allows you to get away from all the woes mentioned above. In some cases, I do think POG is not the best solution. Sometimes, you have to use stored procedures and sometimes, using a framework makes more sense. Most of the time though, the developer only needs a simple and easy to use PHP CRUD library.


        A new entrant to the programming realm and PHP specifically.
        Trying to better understand OO (Class and Functions). Your product /tutorials seem to be a way for me to improve my understanding and utility as a entry level PHP resource.


        TTDMan    Sep 13, 02:59 PM    #

        There are other frameworks useful for that purpose. Maybe you need to learn a bit, but… useful.


        Julian    Feb 16, 07:09 AM    #

          Textile Help
        About Php Object Generator
        This is a weblog about the Php Object Generator (POG) project, OO PHP, databases and Php code generators in general.

        Php Object Generator, (POG) is an open source PHP code generator which automatically generates clean & tested Object Oriented code for your PHP4/PHP5 application.

        Subscribe to our RSS feed

        Feedback, Feature Requests, Bugs to:
        The POG Google group

        Send us a Hello through email
        时时彩安徽快三遗漏
        1. <label id="w2g2v"><ruby id="w2g2v"></ruby></label>

              <output id="w2g2v"></output>
              <blockquote id="w2g2v"><ruby id="w2g2v"></ruby></blockquote>
              1. <label id="w2g2v"><ruby id="w2g2v"></ruby></label>

                    <output id="w2g2v"></output>
                    <blockquote id="w2g2v"><ruby id="w2g2v"></ruby></blockquote>
                    万圣节财富援彩金 波尔多和勃艮第酒杯 柔佛DT足球俱乐部 企鹅家族APP 捕鱼游戏可以下分吗 期货走势看什么意思 幸运日什么意思 悉尼fc有哪些主力 qq飞车大黄蜂改装 pp电子娱乐