#33647: bulk_update silently truncating values for size limited fields
-------------------------------------+-------------------------------------
     Reporter:  jerch                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  4.0
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by jerch):

 Hey Carlton,

 thanks for the headsup. I didnt meant to sound like a drama queen, sorry
 if it came that way. Also I am not eager to push my ideas through at any
 price, since I could be totally on the wrong track, simply for reasons
 I've overlooked. So it is more about getting feedback at all, whether
 things go into the right direction or not.

 What I've learned from >20ys OSS contributions - giving ppl early feedback
 helps to keep them engaged, and lowers the risk of time consuming dead end
 implementations (time on both ends, the implementer and the
 reviewers/maintainers), esp. when the bigger picture needs to be addressed
 (API changes, bigger codebase changes involved at several places). I know
 that django is a very big codebase with lots of legacy, which imho makes
 it even harder for someone from outside to get involved. This for sure is
 a balancing act to maintain. Ofc slow pace is not a bad thing - in fact I
 like django for not buying every shiny new idea in town, as it gives very
 solid development experience (using django myself since version 0.8).
 At this point I wonder if the separated issue tracker in trac vs. repo in
 github might be part of a communication/transfer issue? (At least for me
 as maintainer of several projects github/gitlab made conceptual
 discussions and overall communications alot easier than back in
 SVN/mailing list times...)

 I hope I did not derail this issue too much. :)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33647#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" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070180651c2fa4-0626f7b0-e7bb-45d2-8c8f-71b76d1f31b9-000000%40eu-central-1.amazonses.com.

Reply via email to