way to give you
> a chance to make a new design.
>
> Avraham
>
> On Wed, Feb 3, 2016 at 6:02 PM, Joshua Pokotilow > wrote:
>
>> The service uses the Django REST Framework and takes multiple seconds to
>> return a response. The response is a JSON array with thousands
exists, _then_ let them gather
> real statistics about real problems when they want to change something.
>
> You can have scalibility issues and solve them with whatever framework,
> Django included.
>
> Remco Gerlich
>
>
> On Wed, Feb 3, 2016 at 4:30 PM, Joshua Pokotilo
rement stage
> produces more problem that selecting programming language.
>
> Many thanks,
>
> Serge
>
>
> +380 636150445
> skype: skhohlov
>
> On Wed, Feb 3, 2016 at 5:30 PM, Joshua Pokotilow > wrote:
>
>> At the startup where I work, we'v
be right to want to move off
> Django. We don't know much about your particular circumstances.
>
> For more information on optimizing Django for scale, check out this book.
> https://highperformancedjango.com/
>
> Best of luck.
>
> Bill
>
>
>
>
2016 at 10:46:25 AM UTC-5, Avraham Serour wrote:
>
> what do you mean by slow? can you measure in ms?
>
> On Wed, Feb 3, 2016 at 5:30 PM, Joshua Pokotilow > wrote:
>
>> At the startup where I work, we've written a lot of our server code in
>> Django. So far, we&
At the startup where I work, we've written a lot of our server code in
Django. So far, we've adopted a "build it fast" mentality, so we invested
very little time in optimizing our code. A small amount of load testing has
revealed our codebase / infrastructure as it stands today needs to run
fas
y-django-admin/> and
> utilized the options on the ModelAdmin object
> <https://docs.djangoproject.com/en/1.8/ref/contrib/admin/#modeladmin-options>
> to make it as convenient as possible. Never had any complaints, it's pretty
> straightforward and still allows you
move to a newer Django version
>> and the interface changes/
>>
>> You can make it work, but in many instances it will save you less effort
>> than you though (might even be harder).
>>
>> A few custom views are pretty easy to roll out.
>>
>> On Wed, S
than you though (might even be harder).
>
> A few custom views are pretty easy to roll out.
>
> On Wed, Sep 23, 2015 at 4:00 PM, Joshua Pokotilow > wrote:
>
>> Hello! I just had a fairly lengthy conversation with my colleagues about
>> whether or not Django admin i
Hello! I just had a fairly lengthy conversation with my colleagues about
whether or not Django admin is well-suited to external users outside our
company. I took the position that for certain use-cases, exposing Django
admin to third parties makes a lot of sense, given that the admin
applicatio
case you're *doing validation that requires access to more than a single
> field.*
>
> What sounds vague to you in the documentation?
>
> Le vendredi 21 mars 2014 19:43:07 UTC-4, Joshua Pokotilow a écrit :
>>
>> Given these models, would UserProfile.clean() make sen
Given these models, would UserProfile.clean() make sense as written?
class PhoneNumber(models.Model):
user = models.ForeignKey(User, related_name='phone_numbers')
phone_number = models.CharField(max_length=20)
class UserProfile(models.Model):
user = models.OneToOneField(User)
sm
12 matches
Mail list logo