I think your article would be better written if it contained:
- An overview of ORM issues in general, and how we represent database stuff in the database as objects- with specific regard to the patterns used in load / save methods
- A review of several existing ORM systems, and how they tackle the problem
- A comparison between existing ORMs and yours, and why yours is better.
This would seem to be a better structure.
I don't want to sound discouraging, but you may want to be slightly more scientific in your approach. You should read your own article, and ask the obvious questions, and put the answers in before people do stuff like this:
Many times programmers use classes to interact and display information from a database table.
When? Cite one or more well-known applications which are known to do so. What is the rationale for doing so? Are there any drawbacks in doing so?
While this can be very efficient,
This statement has no evidence to back it up. Cite something relevant.
on a large scale this can be devastatingly slow if not done in the proper manner.
I know that subsequently you do explain this a little, but it would be better if we had some hard facts at this stage; quote results of your benchmarks.
Effectively manage the number of queries between your database and your php script.
Explain what this means. The number of queries at runtime, or the number of distinct TYPES of query. What is the advantage in doing this? Are there any drawbacks?
Avoid "repetitive" queries by getting all needed information once, storing all information in an array or matrix, and appropriately distribute the information to your classes.
Again, sounds good, but we really need a better explanation of why this is a good idea, how it's achieved and any drawbacks which exist.
Within the PHP coding world, especially for on-line websites and applications that interact with a database, a common practice is to create a PHP Class for each table in your database.
This is similar to what you've said before. This is no bad thing but you should really elaborate and cite, not merely repeat.
In general I find your style a little bit random and personal, like you were talking to a bloke in a pub. This is alright, but it may cause you credibility issues (your lack of citations, data etc, won't help here).
I'm not going to comment directly on your spelling, grammar, etc, except to say that you might want to get someone to proofread it next time.
Your intentions are highly honourable, and I commend you for this article. I am myself quite interested in ORM, and I find it a very difficult topic which few people appreciate.
For help writing, look at (for example), some of IBM's articles on Developerworks - although many are on quite a basic level, they are generally well written.
Mark
