Fetching all rows in database table - the OOP way?

[eluser]adamp1[/eluser]
The way you mention sounds very like ORM. Basicly objects represent rows in the database. Now of course this can mean combining rows from different tables (linked by relations).

There are some in the Ignited code part of the forum, but the downside is they can be resource heavy.

The other way is custom SQL code to get what you want, in the form you want. Now this is good for large amounts of data since you won't be creating a load of objects you won't maybe use, but it will mean you may re-write the same SQL code (in which case you may need to refacto things)