Re: Does Django care about max_query_params? [feature request]

https://github.com/googleapis/python-spanner-django/pull/774 seems like an open PR is addressing this. On Tuesday, July 5, 2022 at 6:13:32 AM UTC-4 gurov...@gmail.com wrote: > It's Cloud Spanner. We're using `django_spanner` as a 3rd party connector: > https://github.com/googleapis/python-spa

Re: Does Django care about max_query_params? [feature request]

It's Cloud Spanner. We're using `django_spanner` as a 3rd party connector: https://github.com/googleapis/python-spanner-django On Tuesday, June 28, 2022 at 11:36:08 AM UTC+4 Jason wrote: > > What db are you using? This might also be an issue for your db connector > lib > On Monday, June 27, 20

Re: Does Django care about max_query_params? [feature request]

What db are you using? This might also be an issue for your db connector lib On Monday, June 27, 2022 at 10:49:40 AM UTC-4 gurov...@gmail.com wrote: > Hi, all! > > Gotta problem with the number of query params. We're using a backend, > which connects to a cloud database, and at some point we s

Does Django care about max_query_params? [feature request]

Hi, all! Gotta problem with the number of query params. We're using a backend, which connects to a cloud database, and at some point we suddenly started getting such an error: *Number of parameters in query exceeds the maximum allowed limit of 950* Appearing on this step: *django/django/cont

Feature request for django permissions

I have a projects with multi branches . I want to make permissions according to branch record. I couldn't add customize django permissions model to make foreign key from branch model. Look here for more

Feature Request: set default model primary key to UUID or something else for entire project

I am aware that I can specify any model's primary key by adding that kwarg to a field within the model. I currently do this with most my models, using UUIDField as the primary key: class MyModel(models.Model): id = models.UUIDField(primary_key=True, default=uuid.uuid4, editable=False) #

Re: Feature request: queryset caching inside a request

On Tue, Nov 8, 2011 at 5:02 PM, Chase wrote: > I agree that the kind of queries that are repeated tend to be light > weight ones. The only reason I started looking at this was due to some > higher than average latency between servers in our hosting > environment. > > When you're spending an extra

Re: Feature request: queryset caching inside a request

I agree that the kind of queries that are repeated tend to be light weight ones. The only reason I started looking at this was due to some higher than average latency between servers in our hosting environment. When you're spending an extra 10m per query, even the light ones count. http://bitkick

Re: Feature request: queryset caching inside a request

On Tue, Nov 8, 2011 at 4:07 PM, Chase wrote: > Has anyone else ever been surprised by the number of duplicate > database queries when looking at the Django debug toolbar output? > > In my application, we have models for Users, Profiles and Companies. > Many of our methods take a user as a paramete

Feature request: queryset caching inside a request

Has anyone else ever been surprised by the number of duplicate database queries when looking at the Django debug toolbar output? In my application, we have models for Users, Profiles and Companies. Many of our methods take a user as a parameter, and then look up the related profile and/or company.

Re: feature request - suppression of newlines from tags

On 04/11/10 Russell Keith-Magee said: > Yes, someone has; although the proposal on the table doesn't involve > adding magic syntax to the template tag itself, but for the parser to > consider a tag on a line by itself as something that doesn't introduce > a newline. > > http://code.djangoproject.

Re: feature request - suppression of newlines from tags

On Thu, Nov 4, 2010 at 10:46 PM, Michael P. Soulier wrote: > Hi, > > I'm templating some javascript which is at times rather picky in parsing > depending on one's browser. It would be nice in some cases to suppress the > newline caused by the insertion of a template tag, like in jsp and erb. > Per

Re: feature request - suppression of newlines from tags

On Thu, Nov 4, 2010 at 2:46 PM, Michael P. Soulier wrote: > Hi, > > I'm templating some javascript which is at times rather picky in parsing > depending on one's browser. It would be nice in some cases to suppress the > newline caused by the insertion of a template tag, like in jsp and erb. > Perh

feature request - suppression of newlines from tags

Hi, I'm templating some javascript which is at times rather picky in parsing depending on one's browser. It would be nice in some cases to suppress the newline caused by the insertion of a template tag, like in jsp and erb. Perhaps something like {% if foo %} newline present {%- if foo %} newlin

feature request - iunique

hi, request: we have: name = CharField("Name",iunique=True) iunique translates into a case insensitive unique reason: Most languages in the planet do not have case. This is peculiar to languages using the roman script. As a result, data entry done by people from non roman script backgrounds gen

Re: Re: possible bug or feature request with extra and where

On Wed, Mar 24, 2010 at 2:57 PM, Henrik Genssen wrote: > Hi, > > thanks for your answer! > Now is there a way to force select_related tables any way in a count? >> >>select_related() is an optimization for data retrieval. It allows you >>to expand a select row to include related objects in a s

RE: Re: possible bug or feature request with extra and where

Hi, thanks for your answer! >>>Now is there a way to force select_related tables any way in a count? > >select_related() is an optimization for data retrieval. It allows you >to expand a select row to include related objects in a single query. > >It only follows the "1" side of "1-N" relations. T

Re: possible bug or feature request with extra and where

On Sun, Mar 21, 2010 at 8:17 AM, Henrik Genssen wrote: > No one any comment on this? > is this the expected behavior? ... >>Now is there a way to force select_related tables any way in a count? select_related() is an optimization for data retrieval. It allows you to expand a select row to include

RE: possible bug or feature request with extra and where

No one any comment on this? is this the expected behavior? Hinnack >reply to message: >date: 12.03.2010 10:56:08 >from: "Henrik Genssen" >to: "Django users" >subject: possible bug or feature request with extra and where > >HI all, > >I have a qu

possible bug or feature request with extra and where

HI all, I have a query: results = table1.objects.select_related('table2') plus adding some filter on it. Now I want to add en extra WHERE. So I do: where = 'asdf=12' results = results.extra(where=[where]) Now if I do a count() on that queryset, all related tables are omitted, that are not need

Re: feature request

On Tue, Nov 17, 2009 at 6:29 AM, Brandon wrote: > How do I request a feature from Django? http://docs.djangoproject.com/en/dev/internals/contributing/#requesting-features It's also worth keeping in mind the release cycle: http://docs.djangoproject.com/en/dev/internals/release-process/#release-c

feature request

How do I request a feature from Django? This one would be simple. I'd like the authenticate method to take an extra boolean argument which would determine if it should treat the username as case sensitive. Default would be True, since it treats it that way already. I understand that passwords wou

Re: Feature request: Generic add/change features (similar to admin)

Thanks Russ. I had seen that, but documentation was scarce and I wanted a faster method (no template writing, django admin css and templates are good enough for my app, no need to recode). It took me a little while, but I've now switched completely to to generic::create_object(). Compared to admi

Re: Feature request: Generic add/change features (similar to admin)

On 5/21/07, jj <[EMAIL PROTECTED]> wrote: > Wouldn't it be cool if generic views supported add/change out of the > box, and the only code to write was a 1-liner equivalent to admin's > "fields=(...,)"? Could the current admin rewrite be the occasion to > factor out this functionality and make it

Feature request: Generic add/change features (similar to admin)

One of the best features of Django admin is the ability to add and edit objects without writing any code OR template. However, no such built-in functionality on the non-admin part of the site. Everyone has to reimplement it on its own, which is cumbersome and difficult to get right or as good. Wo

Feature Request

Hi, During reading and playing with django tutorials and documents, I've found that every user who has modify / delete permission can modify / delete items other user had created. It may be acceptable in some situations but there is other situations that users should modify / delete items of