I think the problem might be not the query itself, but the date ranges that get converted using wrong date format. Do you get the same results if you use real datetime objects instead of strings there? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
- [sqlalchemy] SqlAlchemy limiting returned rows prematurely Mike Driscoll
- [sqlalchemy] Re: SqlAlchemy limiting returned rows pr... Michael Bayer
- [sqlalchemy] Re: SqlAlchemy limiting returned row... Mike Driscoll
- [sqlalchemy] Re: SqlAlchemy limiting returned... Michael Bayer
- [sqlalchemy] Re: SqlAlchemy limiting retu... Mike Driscoll
- [sqlalchemy] Re: SqlAlchemy limiting... Michael Bayer
- [sqlalchemy] Re: SqlAlchemy limi... Maciej Szumocki
- [sqlalchemy] Re: SqlAlchemy ... Mike Driscoll
- [sqlalchemy] Re: SqlAlchemy ... Michael Bayer
- [sqlalchemy] Re: SqlAlchemy ... Mike Driscoll
- [sqlalchemy] Re: SqlAlchemy ... Mike Driscoll
