Sisäänkirjautuminen| Uusi tunnus
FrontPage| Projects| Forums| Search|
^ DaoGen Forums: › Why? › PHP5? › Using ToString() with PHP › Next DaoGen version almost ready! › Create (insert) and Save (update) PHP examples › Support for numeric object types almost ready! › DaoGen 2.1.0 released! › Compliments and minor suggestion › variables within a class › Foreign key constraint in create() › Security issue!!! › auto-generated columns and create method › Oracle BLOB › DAO for cross-table queries › Please help me.. › Please use this forum for DaoGen related stuff › Call-time Pass-By-Reference › DaoGen 2.4.0 has been released! › How can I show relationships? › DaoGen & PHP 5 » PHP4 vs PHP5 and other considerations. › singleQuery example in php › Why are save and delete not synchronized? › Why are save and delete not synchronized? › DTD for generated XML › DaoGen 2.2.2 has been released! › DaoGen 2.0.2 is available. › For a thesis ?? › Extremely good idea ?? how can I ???? › Usability suggestions for DaoGen › Performance of DaoGen with Mapping tools › Performance with List › Some usage statistics › DaoGen 2.2.1 has been released! › Programming Examples are back! › DaoGen 2.0.1 is available. › Version 2.0.0 generates buggy PHP code! New version soon available! › Examples of DaoGen customizations › Code Examples
» Käyttäjätunnus:
» Salasana:
» Muista kirjautuminen:
Suosituimmat sivut: › DaoGen Forums › Using ToString() with PHP » PHP4 vs PHP5 and other considerations. › Programming Examples › Projects › Search › DaoGen FAQ › DaoGen Manual › How can I show relationships? › Programming Examples are back!
FrontPage » Forums » DaoGen Forums » PHP4 vs PHP5 and other considerations.

PHP4 vs PHP5 and other considerations.

Posted by anonymous 12.11.2005 00:15

Your simple little web app has become a primary tool for me as I am learning java. I would like to make a few suggestions:

1) You should have PHP5 code generation... currently you are using limited and deprecated object functionality from php4. PHP5 is almost as elegant as Java at this point, and porting java to php5 is a snap.

2) You should allow people to download a 'schema generator" tool that would allow for the easy and fast modeling of someone's existing database... creating one XML per table when given a database DSN.

3) You should consider creating a superclass for all DAO object that contain common and redundant code - including the storage of the connection object itself.

Re: PHP4 vs PHP5 and other considerations.

Posted by anonymous 27.01.2006 23:51

If you look up the J2EE Data Access Object pattern specifications from Sun you will find a nice solution using the Factory pattern. By creating a DAOFactory you can encapsulate all of the database access code in one location and generate all of your Data Access Objects from this one instance.

This is a nice little utility however for the most part I tend to write my DAO's by hand... it would be nice if the source code from DAOGEN was open-source just like the generated PHP is supposed to be :)