Hello Craig,
There's unfortunately no way to hook into the migration auto-detector to
specify
additional operations to be added.
What I suggest you do instead is dynamically inject operations in the plan
that
is about to be run by connecting a pre_migrate signal. When you detect
CreateModel ope
Hi there
I'm in the early stages of developing a third party app which makes heavy
use of postgres extensions. The app provides an abstract model, so I won't
have direct control of user's models or migrations. I'm having trouble
getting it to generate sensible migrations for users.
At present the
I was just thinking that changing the js widget would not require to
rewrite the python code, barely the js widget support. I'm not trying
to push it, just make sure we are taking the right facts into
consideration, but I'm happy with select2 myself.
--
You received this message because you are s
On Tuesday, June 6, 2017 at 11:54:16 AM UTC+2, Johannes Hoppe wrote:
>
> I think we made some good progress in the regarding this issue. The
> inclusion of select2 is at a stage where I wouldn't want to jump to a
> different library. Especially considering that now one acted at this ticket
> f
Currently, the DecimalField does not support unlimited precision numeric
fields that are available in db backends. As in the ticket's description
and comments https://code.djangoproject.com/ticket/24920 , there were two
solution proposed: new field, or an update to DecimalField's behavior. I
wa
Thanks for asking, my name is ∞, but you've known my as James Pic /
YourLabs. Nice to speak with you again <3
I think it would make sense for a core dev to advocate against this
change, because we'd be breaking BC before having enough information
to know if this is going to have a generally more p
Hi!
I didn't get your name, but this address the latest post.
I think we made some good progress in the regarding this issue. The
inclusion of select2 is at a stage where I wouldn't want to jump to a
different library. Especially considering that now one acted at this ticket
for seven years an
Hi all,
In our experience, it would be worth removing noConflict, but we need
Django to have a recent jQuery release, it's wasn't always the case but now
it's good. I don't know who relies on that except grappeli, but they would
probably be happy to get rid of their double jquery loading becaus
