Re: 'too many SQL variables' error with ModelMultipleChoiceField

2012-04-23 Thread akaariai
On Apr 23, 6:54 pm, "Daniel Sokolowski" wrote: > +1 > > I use SQlite3 on lower traffic production sites due to it's ease of install > and deployment. Even though I only once I reached this 1000 variable limit I > would like to see some django work around. I thought a little more about this, and I

Re: 'too many SQL variables' error with ModelMultipleChoiceField

2012-04-23 Thread Daniel Sokolowski
jango users Subject: Re: 'too many SQL variables' error with ModelMultipleChoiceField On Apr 23, 10:48 am, Lukas Zilka wrote: Hey Russ, thanks for your reply. I looked at the bulk insertion problem, and that made me think that probably using the variables themselves is the probl

Re: 'too many SQL variables' error with ModelMultipleChoiceField

2012-04-23 Thread akaariai
On Apr 23, 10:48 am, Lukas Zilka wrote: > Hey Russ, > > thanks for your reply. I looked at the bulk insertion problem, and > that made me think that probably using the variables themselves is the > problem. It does not really make sense to me why anybody bothers to > use variables in a long SQL

Re: 'too many SQL variables' error with ModelMultipleChoiceField

2012-04-23 Thread Lukas Zilka
Hey Russ, thanks for your reply. I looked at the bulk insertion problem, and that made me think that probably using the variables themselves is the problem. It does not really make sense to me why anybody bothers to use variables in a long SQL query for the IN clause, let alone a bulk insertion? D

Re: 'too many SQL variables' error with ModelMultipleChoiceField

2012-04-23 Thread Lukas Zilka
Thanks for your reply Anssi. My previous post probably got lost somewhere (or maybe just awaiting moderation?), so I am going to repeat the relevant part. It is related with your point on qs.filter(id__in=large_list), so I will try to say it again. Why do you use SQL variables when you construc

Re: 'too many SQL variables' error with ModelMultipleChoiceField

2012-04-23 Thread akaariai
On Apr 23, 1:43 pm, Javier Guerra Giraldez wrote: > On Mon, Apr 23, 2012 at 3:58 AM, akaariai wrote: > > The last one, qs.filter(id__in=large_list) is pretty much impossible to fix. > > what's wrong with: > > qs.filter((Q(id__in=large_list[:n])|Q(id__in=large_list[n:])))  ? > > >   1. Use differe

Re: 'too many SQL variables' error with ModelMultipleChoiceField

2012-04-23 Thread Javier Guerra Giraldez
On Mon, Apr 23, 2012 at 3:58 AM, akaariai wrote: > The last one, qs.filter(id__in=large_list) is pretty much impossible to fix. what's wrong with: qs.filter((Q(id__in=large_list[:n])|Q(id__in=large_list[n:]))) ? >   1. Use different database. I guess you have a reason to use SQLite so this > m

Re: 'too many SQL variables' error with ModelMultipleChoiceField

2012-04-23 Thread akaariai
On Monday, April 23, 2012 1:56:19 AM UTC+3, Russell Keith-Magee wrote: > > It's also probable that it's something that is new to 1.4 (or, at least, > that it manifests in slightly different ways in 1.4). One of the features > added in 1.4 is bulk insertion of data. This means that you can use a

Re: 'too many SQL variables' error with ModelMultipleChoiceField

2012-04-22 Thread Russell Keith-Magee
Hi Lukas, I haven't looked into the problem in detail, but it doesn't surprise me that it exists. It's also probable that it's something that is new to 1.4 (or, at least, that it manifests in slightly different ways in 1.4). One of the features added in 1.4 is bulk insertion of data. This mea

'too many SQL variables' error with ModelMultipleChoiceField

2012-04-22 Thread Lukas Zilka
Hello, I have a form with ModelMultipleChoiceField on it, and I am getting 'DatabaseError: too many SQL variables' (using SQLite) when the user picks more than 1000 entries in the selection widget and posts the form. The problem seems to be the method clean of ModelMultipleChoiceField, which trie