im not sure what youre trying to do that you cant just do with the offset and limit parameters. are you trying to avoid creating a select object, and then the mapper creating a second one internally ? you can send a full select object to the mapper: s = select(Campaign.c) s.limit = limit s.offset = offset total = s.count().scalar() rows = mapper.select(s) but that is not going to work with eager loading, since LIMIT and OFFSET work in a more complicated way in that case, like the docs mention...there might also be other difficulties with creating your own column clause. if its the select's conditions that are so important, you can hold onto the WHERE condition separately and send that to your select() and mapper.select() method. if you tell me what you really need to do that would help. On Mar 22, 2006, at 4:43 PM, Qvx 3000 wrote: Yes, I know about it. I'm currently using limit and offset up-front, just like I said at the end of my post. I was asking for a way to do it later - after I have constructed select. The only way I see is using plain select but I get tuples as a result. |
- [Sqlalchemy-users] deferring mapper selects Qvx 3000
- Re: [Sqlalchemy-users] deferring mapper selects Michael Bayer
- Re: [Sqlalchemy-users] deferring mapper selects Qvx 3000
- Re: [Sqlalchemy-users] deferring mapper selects Michael Bayer
- Re: [Sqlalchemy-users] deferring mapper sel... Qvx 3000
- Re: [Sqlalchemy-users] deferring mappe... Michael Bayer
- Re: [Sqlalchemy-users] deferring mapper selects Todd Grimason
- Re: [Sqlalchemy-users] deferring mapper selects Todd Grimason