Re: [sqlalchemy] too many SQL variables in in_

2014-09-13 Thread pyArchInit ArcheoImagineers
Il giorno giovedì 11 settembre 2014 18:39:24 UTC+2, Jonathan Vanasco ha scritto: i once thought about extending SqlAlchemy to handle this issue behind the scenes, but each database treats `IN()` differently. for example: oracle maxes out at a number of elements, while mysql maxes out based

Re: [sqlalchemy] too many SQL variables in in_

2014-09-13 Thread Wichert Akkerman
On 13 Sep 2014, at 11:25, pyArchInit ArcheoImagineers pyarchi...@gmail.com wrote: Il giorno giovedì 11 settembre 2014 18:39:24 UTC+2, Jonathan Vanasco ha scritto: i once thought about extending SqlAlchemy to handle this issue behind the scenes, but each database treats `IN()`

Re: [sqlalchemy] too many SQL variables in in_

2014-09-13 Thread pyArchInit ArcheoImagineers
I had a mystical appearence!!! I will put in a dictionary the parameters of searching used in the GUI. If I would to sort the record, the script will re-do the search, which at this time will use only a few parametrs, and I'll put an ORDER_BY in the query. The script will write dinamically as

Re: [sqlalchemy] too many SQL variables in in_

2014-09-11 Thread Michael Bayer
On Sep 11, 2014, at 1:53 AM, pyArchInit ArcheoImagineers pyarchi...@gmail.com wrote: Hi, if I create many or request with a little number of id (list populated with 10 values), the script return to me this message: Expression tree is too large (maximum depth 1000) So, It's possibile

Re: [sqlalchemy] too many SQL variables in in_

2014-09-11 Thread Jonathan Vanasco
i once thought about extending SqlAlchemy to handle this issue behind the scenes, but each database treats `IN()` differently. for example: oracle maxes out at a number of elements, while mysql maxes out based on the size of the overall statement (which is configured on the server). it's too

Re: [sqlalchemy] too many SQL variables in in_

2014-09-10 Thread pyArchInit ArcheoImagineers
Hi, if I create many or request with a little number of id (list populated with 10 values), the script return to me this message: Expression tree is too large (maximum depth 1000) So, It's possibile there is a limit for sqlite? This is a big problem for using sqlalchemy/sqlite. I cannot

Re: [sqlalchemy] too many SQL variables in in_

2014-09-09 Thread pyArchInit ArcheoImagineers
Hi Michael and thanks a lot. Il giorno venerdì 5 settembre 2014 18:23:31 UTC+2, Michael Bayer ha scritto: you batch out the values to be used in the IN, then one of two choices: my preference is to run separate SELECT statements, using IN with each batch. If you really can’t do that, you

Re: [sqlalchemy] too many SQL variables in in_

2014-09-09 Thread Michael Bayer
On Sep 9, 2014, at 4:45 PM, pyArchInit ArcheoImagineers pyarchi...@gmail.com wrote: Hi Michael and thanks a lot. Il giorno venerdì 5 settembre 2014 18:23:31 UTC+2, Michael Bayer ha scritto: you batch out the values to be used in the IN, then one of two choices: my preference is to run

Re: [sqlalchemy] too many SQL variables in in_

2014-09-09 Thread pyArchInit ArcheoImagineers
Hi Michael, I use my method for every tables of my DB so I pass the mapper class, the name of id, etc, etc. and through a string I build the cmd to pass to the eval function. I'll try your method.. Thanks a lot. Best regards Luca Il giorno martedì 9 settembre 2014 22:58:59 UTC+2, Michael

[sqlalchemy] too many SQL variables in in_

2014-09-05 Thread mando
Hi to all, I wrote a method like this to reuse the code for many tables at the same time[0] But, with more than 1000 records sqlite doesn't accepts the amount of id inside .in_(id_list) How can I filter, split or can manage it? Thanks a lot and best regards, Luca [0] def

Re: [sqlalchemy] too many SQL variables in in_

2014-09-05 Thread Michael Bayer
you batch out the values to be used in the IN, then one of two choices: my preference is to run separate SELECT statements, using IN with each batch. If you really can't do that, you can combine the batches of IN groups with an OR: x IN (batch1) OR x IN (batch2) ... keep in mind when you