ok. thank you.

@xentek

I still don't get the downside of including the table name, don't all the databases accept that kind of very basic queries?

I do have a problem with switching to fetchAll since you then can argue: why have a find() at all? I think this small change would allow a higher flexibility; the manual mentions joins but not much of all the functions that are affected by this change. Both the find() and the _getWhereQuery() in the table row are affected by it (probably even more)...

Find is intended for one line queries that look up off primary key id. fetchAll has the flexiblity to handle more complex queries.

If you need something more than:

SELECT * FROM table WHERE id = 0

Then you've shot past find's intended use. That's all I'm arguing.