Re: data sharing with multiple clients by server simultaneously

This mailing list is for the development of Django itself, not for support using Django. Please use the django-users mailing list for that, or IRC #django on freenode, or a site like Stack Overflow. On Tue, 29 Jan 2019 at 17:51, shiva kumar wrote: > Hi guys. I have a doubt regrading

Re: Google Summer of Code 2019

Thanks for the input Carlton and Adam. I will start working on the POC then. On Tuesday, January 29, 2019 at 11:41:48 PM UTC+5:30, Adam Johnson wrote: > > Small point: a cross-DB JSONField could also serve as a cross-DB > ArrayField, since JSON can store arrays. I don't believe MySQL or SQLite

data sharing with multiple clients by server simultaneously

Hi guys. I have a doubt regrading communication b\w client and server. consider an example there are 20 clients continuously connected and share data with server and server response to there request. my requirements are What are all the concepts needed inorder to make it? and some alternatives.

Re: Google Summer of Code 2019

Small point: a cross-DB JSONField could also serve as a cross-DB ArrayField, since JSON can store arrays. I don't believe MySQL or SQLite have "array" types, so to build a cross-DB ArrayField you'd emulate them with JSON plus a restriction to just storing arrays, which comes back to building a

Re: Google Summer of Code 2019

Hi Shrikrishna, Not so much a ticket… See the thread I linked. There’s a lot of info there. The first step (I think) is a proof-of-concept JSONField for SQLite — we have the other three DBs. So taking a look at the implementation of the existing fields and SQLite’s API for the JSON

Re: database configuration error(django and mysql)

Desh, as Adam already mentioned to you once before: > This mailing list is for the development of Django itself, not for support > using Django. Please use. the django-users mailing list for that, or IRC > #django on freenode, or a site like Stack Overflow. ___ Nick Perry 404.660.1020

database configuration error(django and mysql)

Forbidden (403) CSRF verification failed. Request aborted. Help Reason given for failure: CSRF token missing or incorrect. In general, this can occur when there is a genuine Cross Site Request Forgery, or when Django's CSRF mechanism has

Re: Google Summer of Code 2019

Hello Carlton, I am interested to do a GSoC project based on this idea and looking forward to researching on this topic and drafting a proposal. In the mean, can you please suggest me any easy picking ticket(related to this idea) I should work on? Thanks, Shrikrishna -- You received this

Re: Proposal to re-open #27017 (updating only dirty fields in save())

While I'm not sure I have any particular suggestion for this, the problem is important enough for a few of the projects I'm maintaining. I have implemented more than a few custom save() methods, post_init/pre_save/post_save signals and complicated ways of setting update_fields and acting on their

Re: revisiting the Python version support policy

Yep, I'm definitely in favor of dropping 3.5 early and using all the nice features extensively. Especially type annotations. All projects I work on use 3.6 or later for quite some time now, whatever debian guys might feel about stability. Ivan. On Wed, Jan 23, 2019 at 12:16 PM Josh Smeaton

Re: Google Summer of Code 2019

Maybe, we could append this idea with the 'Improve less popular database backend idea' on the wiki page as that project is also not that big for a GSoC project but the purpose of both projects seems

Re: BitBounce Spam Replies From the Mailing List

Sorry for resurrecting but this is still very much a problem. Same person, same autoresponder. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from

Re: Proposal to re-open #27017 (updating only dirty fields in save())

I feel conflicted here as I've spent numerous hours under different contracts fixing bugs caused by missing update_fields and leading to data loss or inconsistent database states ;) On a more serious note, please make this happen. With concurrent updates calling save() without update_fields is