: 0 |UI/UX: 0
+
Changes (by Karol Alvarado):
* cc: Karol Alvarado (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/22828#comment:10>
Django <https://code.djangoproject.
thing that has to be
noted because it's confusing.
--
Ticket URL: <https://code.djangoproject.com/ticket/22828#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the
=> Aditya Chaudhary
--
Ticket URL: <https://code.djangoproject.com/ticket/35670#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates&qu
: 0
Easy pickings: 0 |UI/UX: 1
---+
Changes (by devday):
* owner: (none) => devday
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/34624#comment:12>
D
#35381: Regression on json null value constraints in django 4.2
-+-
Reporter: Olivier Tabone |Owner: devday
Type: Bug | Status: assigned
|UI/UX: 0
--+---
Changes (by Tom Carrick):
* owner: nobody => Tom Carrick
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/21289#comment:9>
D
Ülgen Sarıkavak):
* cc: Ülgen Sarıkavak (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/34898#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the G
://github.com/django/django/blob/main/django/db/models/fields/__init__.py#L1073
It would be great if after the above line a value passed in the field
(such as `ForeignKey`) could be used to specify items to pass to
`select_related()` or simply to call `select_related()`. Prefetch ability
would also
email"))
> )
> }}}
>
That `User`/`Email` was mostly to exemplify the issue :)
--
Ticket URL: <https://code.djangoproject.com/ticket/35779#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this mess
, consider using .values() or
.values_list() to reduce the amount of data furthe
User.objects.prefetch_related(
Prefetch("email_set", queryset=Email.objects.only("user_id", "email"))
)
--
Ticket URL: <https://code.djangoproject.com/ticket/35779#comment:2>
Dj
-+-
Changes (by GunSliger7):
* owner: (none) => GunSliger7
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/35779#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You rec
) => GunSliger7
--
Ticket URL: <https://code.djangoproject.com/ticket/35615#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
still working in this issue ?
Or shall I assign this to myself ?
--
Ticket URL: <https://code.djangoproject.com/ticket/35670#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed t
compiled before execution (see the linked code
above). Repeat compiling isn't the performance hit here, it's the
backtracking in the pattern itself.
--
Ticket URL: <https://code.djangoproject.com/ticket/35675#comment:3>
Django <https://code.djangoproject.com/>
The Web fra
iding repeated compilation overhead for frequent matches?
--
Ticket URL: <https://code.djangoproject.com/ticket/35675#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to
being thrown into the trash, but also because the
iteration was taking some time to happen (very large table), some related
objects got deleted in the meantime, and when the ORM tried to
`refresh_from_db` to get the related id, it failed with that error.
--
Ticket URL: <https://code.djangopr
But I'm happy to be swayed.
--
Ticket URL: <https://code.djangoproject.com/ticket/35778#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
&quo
https://github.com/django/django/pull/18549
>
> It is possible to use the native JSONObject with server side bindings,
> but it requires a little bit of use of `cast`.
>
> See find it again>
>
> There are two minor issues:
>
> 1. Should Postgres 16 *without* server
):
I've created the separate ticket to track use of the native json object
with postgres 16+ and server side bindings:
https://code.djangoproject.com/ticket/35778#ticket
--
Ticket URL: <https://code.djangoproject.com/ticket/35734#comment:15>
Django <https://code.djangoproject.com/>
with server side bindings recently resulted in a
crash. The most recent fix is to fallback to the use of jsonb_build_object
on postgres 16 when using server side bindings.
See https://code.djangoproject.com/ticket/35734
And https://github.com/django/django/pull/18549
It is possible to use the
ix, 'name':
self.name}
path = "%s.%s" % (self.__class__.__module__,
self.__class__.__name__)
return path, self.expressions, kwargs
def clone(self):
return self.__class__(self.column, self.prefix, self.name)
}}}
--
Ticket URL: <https://code.dj
an option.
--
Ticket URL: <https://code.djangoproject.com/ticket/35777#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates"
):
Replying to [comment:11 Sarah Boyce]:
>
[https://github.com/django/django/commit/0f53d48115ba0295cefea33512dc146caad39443
Here is an approach] which uses the native `JSONObject` function for
server side bindings, casting the keys to text. Adding it here for a
record.
I can create a separ
):
* summary: Tests fail with Postgres 16 and server side bindings =>
JSONObject crashes with Postgres 16 and server side bindings
--
Ticket URL: <https://code.djangoproject.com/ticket/35734#comment:13>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists
om/doc/refman/8.4/en/create-index.html#create-index-
column-prefixes. So called `Column Prefix Key Parts`.
--
Ticket URL: <https://code.djangoproject.com/ticket/35777#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You rec
ach in the OP. That index however
is useless. It cannot be used by MySQL for speeding up `startswith`
queries.
--
Ticket URL: <https://code.djangoproject.com/ticket/35777#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
Yo
using
[https://docs.djangoproject.com/en/5.0/ref/models/indexes/#django.db.models.Index.expressions
Index.expressions] and [https://docs.djangoproject.com/en/5.0/ref/models
/database-functions/#left Left]
--
Ticket URL: <https://code.djangoproject.com/ticket/35777#comment:1>
D
y downsides:
* cannot run tests without running the migrations if i need the index in
tests
* makes squashing migrations more painful
But it seems, this is impossible to achieve with the `Meta.indexes`:
{{{
Index(fields=['url(100)'], name='my_limited_prefix_index')
"alpha" backporting
policy. Therefore, this commit is really a "5.0 feature" and it's my
understanding that this does not qualify for a 5.1 backport.
--
Ticket URL: <https://code.djangoproject.com/ticket/35766#comment:10>
Django <https://code.djangop
LL rather
than all.
Regression in 1eac690d25dd49088256954d4046813daa37dc95.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/373#comment:192>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Gro
):
* needs_tests: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/35734#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates&qu
://github.com/django/django/pull/18549/commits/0f53d48115ba0295cefea33512dc146caad39443
Here is an approach] which uses the native `JSONObject` function for
server side bindings, casting the keys to text. Adding it here for a
record.
--
Ticket URL: <https://code.djangoproject.com/ticket/35
-+-
Comment (by Sarah Boyce):
[https://github.com/django/django/pull/18604 PR] - have some questions as
to whether it is required for the backport
--
Ticket URL: <https://code.djangoproject.com/ticket/35766#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for pe
):
* needs_better_patch: 1 => 0
* needs_docs: 1 => 0
* needs_tests: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/35462#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this me
-+-
Comment (by Sarah Boyce):
Yes you're right - I missed this. I will create a release note a back port
shortly
--
Ticket URL: <https://code.djangoproject.com/ticket/35766#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
antoliny0919):
* needs_better_patch: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/35742#comment:20>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google
run the tests with
>
> {{{
> python runtests.py postgres_tests.test_array
> }}}
>
> The test passes, does this mean that the bug has been resolved?
Nevermind, ignore this
--
Ticket URL: <https://code.djangoproject.com/ticket/35449#comment:9>
Django <https://code.d
he sequence to the next
available value, instead of keeping the manually-set value of the
sequence.
--
Ticket URL: <https://code.djangoproject.com/ticket/35763#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You receive
-+-
Comment (by Claude Paroz):
Isn't the related commit 07fa79ef2bb3e8cace7bd87b292c6c85230eed05 ?
--
Ticket URL: <https://code.djangoproject.com/ticket/35766#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You rece
m/ticket/35772#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving email
://forum.djangoproject.com/t/ticket-18392-and-mysql-
utf8mb4/34916 forum thread] about this.
--
Ticket URL: <https://code.djangoproject.com/ticket/18392#comment:54>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message
support for GDAL 3.0.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35776#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Dja
ady for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/35776#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates&qu
ticket/35776#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails f
er top-bottom pass. Once the minor nitpicks are fixed, I
need to do a in-depth review in terms of test coverage and functionality.
--
Ticket URL: <https://code.djangoproject.com/ticket/35535#comment:21>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists
houghts on this.
--
Ticket URL: <https://code.djangoproject.com/ticket/33230#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" grou
s://code.djangoproject.com/ticket/35734#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group
226bc1c52a0165164e5b34fef1d336050ca60"
Fixed #35748 -- Documented that fields are excluded from a ModelForm when
formfield() returns None.
Co-authored-by: Sarah Boyce <42296566+sarahbo...@users.noreply.github.com>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35748#comment:
-+-
Changes (by Sarah Boyce):
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/35748#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you
ut removing the reference, or leaving it as is, un-referenced?
--
Ticket URL: <https://code.djangoproject.com/ticket/35772#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to
lly disagree. I change the auto increment value of my table,
and Django's migration undoes this.
--
Ticket URL: <https://code.djangoproject.com/ticket/35763#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received thi
et URL: <https://code.djangoproject.com/ticket/35774#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscr
et URL: <https://code.djangoproject.com/ticket/35775#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscr
et URL: <https://code.djangoproject.com/ticket/35776#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscr
ould have to be officially
documented. Having it in there while maintaining its status as a private
part of the API is a bit in the gray area.
--
Ticket URL: <https://code.djangoproject.com/ticket/35772#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionis
-+-
Comment (by Natalia Bidart):
Replying to [comment:4 Kevin Renskers]:
> It really does feel like a Django bug to me though. It only breaks using
SQLite, and only when adding a second migration.
Are you saying that further migrati
-+-
Comment (by Natalia Bidart):
Replying to [comment:5 Claude Paroz]:
> Sarah, isn't this a regression in the last Django version that warrants
a backport?
Hey Claude, thanks for keeping an eye on things!
But the feature was introduced in 5.0 so it does not qualify for a
backport
-+-
Comment (by Natalia Bidart):
Replying to [comment:5 Claude Paroz]:
> I suspect that this issue could be related to the fact that SQLite AFAIR
doesn't support adding columns, so Django is emulating that by deleting
and recrea
improvement: 0
Easy pickings: 0 |UI/UX: 0
--+
Changes (by Sarah Boyce):
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/35776#comment:1>
Djan
improvement: 0
Easy pickings: 0 |UI/UX: 0
--+
Changes (by Sarah Boyce):
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/35775#comment:1&g
;https://code.djangoproject.com/ticket/35774#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop
#24686: Support for Moving a model between two Django apps
---+
Reporter: Alex Rothberg |Owner: Bhuvnesh
Type: New feature| Status: assigned
Component: Migrations
--
Ticket URL: <https://code.djangoproject.com/ticket/35776>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe fr
].
--
Ticket URL: <https://code.djangoproject.com/ticket/35775>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe fr
| Patch needs improvement: 0
Easy pickings: 0|UI/UX: 0
-+-
GEOS 3.8 will be more than 5 years old when Django 5.2 is released.
https://libgeos.org/usage/download/
--
Ticket URL
Boyce):
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/35742#comment:19>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google
est crash if PyYAML isn't
installed.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29522#comment:26>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
&
63808b7d1b115"
Fixed #35074 -- Fixed adding/removing indexes when spatial_index is
changed on MySQL, PostgreSQL, and Oracle.
Co-authored-by: Mário Falcão
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35074#comment:22>
Django <https://code.djangoproject.com/>
The Web
-+-
Comment (by Claude Paroz):
Sarah, isn't this a regression in the last Django version that warrants a
backport?
--
Ticket URL: <https://code.djangoproject.com/ticket/35766#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Sarah Boyce):
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/35074#comment:21>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to th
-+-
Changes (by Jacob Walls):
* has_patch: 0 => 1
* owner: Jeetu Singh => Jacob Walls
Comment:
[https://github.com/django/django/pull/18597 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/35308#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for p
: Neil Pendyala => Aditya Chaudhary
--
Ticket URL: <https://code.djangoproject.com/ticket/35095#comment:22>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
still required ?
--
Ticket URL: <https://code.djangoproject.com/ticket/13883#comment:33>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django u
following
code. This code can be added to the ready() method of an AppConfig class
in one of your INSTALLED_APPS, which is a more integrated and commonly
used approach:``
--
Ticket URL: <https://code.djangoproject.com/ticket/35770#comment:4>
Django <https://code.djangoproject.com/
(by Aditya Chaudhary):
* owner: (none) => Aditya Chaudhary
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/35770#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this m
the defaults in django to "utf8mb4", but put prominent
notes in the documentation for how users can set the database options to
use "utf8mb3"? We could link to a page like
[https://dev.mysql.com/doc/refman/9.0/en/charset-unicode-conversion.html
this], and then users could sta
)
--
Ticket URL: <https://code.djangoproject.com/ticket/18392#comment:52>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To
ef3fc2055e4be8b9602ac9"
Fixed #35766 -- Handled slices in BaseChoiceIterator.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35766#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message be
-+-
Changes (by Sarah Boyce):
* stage: Accepted => Ready for checkin
Comment:
PR received approval
--
Ticket URL: <https://code.djangoproject.com/ticket/35766#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You receiv
):
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/33537#comment:13>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Djang
#35773: Error importing HeaderWriteError from email.errors after upgrading to
Django 4.2.16
--+--
Reporter: Muzaffar Omer |Owner: (none)
Type: Bug | Status
Jae Hyuck Sa ):
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/35667#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
delCreation#InstallingTheAttributes
Django's Wiki 2006]
* [https://lazypython.blogspot.com/2008/11/django-models-digging-little-
deeper.html Alex Gaynor's post 2008]
* [https://www.b-list.org/weblog/2019/mar/04/class/ James Bennet's post
2019]
* [https://jacobian.org/til/django-model-fields-with-a
#35773: Error importing HeaderWriteError from email.errors after upgrading to
Django 4.2.16
--+--
Reporter: Muzaffar Omer |Owner: (none)
Type: Bug | Status
#35773: Error importing HeaderWriteError from email.errors after upgrading to
Django 4.2.16
--+---
Reporter: Muzaffar Omer | Type: Bug
Status: new |Component
ket/35676#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from
/django/django/blob/9ca1f6eff6f19d1ae074d289c6c4209073351805/django/db/models/fields/__init__.py#L957-L958]
and in the
docs[https://docs.djangoproject.com/en/5.1/ref/models/instances/#django.db.models.Model.get_previous_by_FOO],
it is suggested that a user may override `Field.contribute_to_class
o try to tackle it and put up a PR if there are no
objections.
Are you still working on the issue ?
if not, I'd like to try have a go on it :)
--
Ticket URL: <https://code.djangoproject.com/ticket/34624#comment:11>
Django <https://code.djangoproject.com/>
The Web framewor
h: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/2750#comment:26>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates&qu
Jae Hyuck Sa ):
* owner: (none) => Jae Hyuck Sa
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/35667#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this messa
-+-
Changes (by Sarah Boyce):
* resolution: => duplicate
* status: new => closed
Comment:
Duplicate of #32320
--
Ticket URL: <https://code.djangoproject.com/ticket/35771#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with d
4, 9, 17)
"""
I figured it out myself and in `pre_save` function of models.DateField
class, we should use timezone.now().date() instead of
datetime.date.today()
""
}}}
--
--
Ticket URL: <https://code.djangoproject.com/ticket/35771#comment:1>
Django <h
ield
class, we should use timezone.now().date() instead of
datetime.date.today()
"""
--
Ticket URL: <https://code.djangoproject.com/ticket/35771>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this messag
-+-
Changes (by bcail):
* cc: bcail (added)
Comment:
I know this was closed as a duplicate, but could we please look into re-
opening it? I've opened a [PR https://github.com/django/django/pull/18593]
that tests changing a CharField to a Text
-+-
Comment (by Claude Paroz):
I suspect that this issue could be related to the fact that SQLite AFAIR
doesn't support adding columns, so Django is emulating that by deleting
and recreating the entire table to add new columns. I
erson):
Similar to #9475, I think this "through" restriction is pretty artificial
at this point (since #6707 and #9475) and the restriction can probably be
removed.
Example PR here: https://github.com/django/django/pull/18594 (I don't
plan on pushing this through myself but feel
eally does feel like a Django bug to me though. It only breaks using
SQLite, and only when adding a second migration. The initial adjustment of
the auto increment value works just fine using a proper documented query,
not via a workaround where we're creating a dummy object. But once I add
-+-
Changes (by Natalia Bidart):
* resolution: => invalid
* status: assigned => closed
Comment:
Hello Kevin, thank you for your report.
It's unclear that this qualifies as a bug report for Django. This may be
better sui
fix for that already (reverted the revert) in my tree.
Then in that case we definitely need a reliable way to reproduce this.
This could be a minimal Django test project, or the model and admin
definitions that would showcase this issue.
Please re-open when you can provide that.
Thank you!
--
specifically, but seems like there are better way to put code that needs
to always run.
--
Ticket URL: <https://code.djangoproject.com/ticket/35770#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message bec
1 - 100 of 47648 matches
Mail list logo
