> Don't you think that fetchFirst() would be more describing than > fetchAny() for a method that returns exactly first record it met from > the underlying resultset (of course returning null if it met nothing)?
This is a common pattern I have encountered various times with EJB entity beans, 10 years ago already. Sometimes (In quite rare occasions), you're interested in fetching arbitrary records from the database. If the method is called "fetchAny", I can still change the underlying implementation (e.g. ignore ordering). If it is called "fetchFirst", this would be the same as adding limit(1) to the query...
