LIMIT NULL and LIMIT ALL per the PG docs at http://www.postgresql.org/docs/9.0/static/queries-limit.html are the same as omitting the number. These would appear to be syntactical helpers that you wouldn't really need when working with a select() construct (unless you're trying to get at some PG optimizer quirk).
so why exactly do you need to emit these otherwise unnecessary keywords ? On Mar 20, 2014, at 5:29 PM, Ryan Kelly <[email protected]> wrote: > Hi: > > It seems that the argument to query.limit must be a number. However, > NULL (which I imagine could be passed by the null() construct or as a > string) and ALL (which, I suppose could be text("ALL") or > literal("ALL") or just the string "ALL") are perfectly acceptable > values on PostgreSQL. > > Is there some way to convince SQLAlchemy to render these values? > > -Ryan Kelly > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
