Doctrine 2 - ORM

MySQL Failure when using setFirstResult() and omitting setMaxResults()

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.1.4
  • Fix Version/s: None
  • Component/s: None
  • Security Level: All
  • Labels:
    None

Description

When using setFirstResult() and omitting setMaxResults(), MySQL throws an error. This was very confusing for me until I dumped the SQL statements and found out the reason.

I know that MySQL doesn't directly support this, their manual says that you should set the second parameter to LIMIT to a very high number (18446744073709551615 in their example).

I'd recommend that either throwing an error in the specific platform driver or follow the MySQL example.

Activity

Hide
Permalink
Benjamin Eberlei added a comment -

Changed into improvement, i am not sure how this relates to other databases.

You can just use this workaround yourself so long.

Show
Benjamin Eberlei added a comment - Changed into improvement, i am not sure how this relates to other databases. You can just use this workaround yourself so long.

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    Timo A. Hummel
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: