for most ORM's the typical access path is
single table selects either for:
- a primary key (for a single record)
- a list of related records (ie.. a foreign key)
- and possibly a '%XXX%' to match a name or something
Is the
HANDLER functionality a better (ie faster) method than using SQL syntax in this case?
it seems like a more natural 'fit' for the ORM type behavior.