Re: Non-atomic migrations in Django?

2015-11-29 Thread Ludwig Hähne 
Thanks for your feedback and support. I've opened a ticket and pull request:

https://code.djangoproject.com/ticket/25833

Am Dienstag, 24. November 2015 21:05:04 UTC+1 schrieb Markus Holtermann:
>
> Hi Ludwig, 
>
> the API looks clean and sensible to me. +1 for getting that into 1.10 
>
> /Markus 
>
> On November 25, 2015 12:00:59 AM GMT+10:00, "Ludwig Hähne" <
> lha...@gmail.com > wrote: 
> >Hi all, 
> > 
> >I'd like to get your feedback on supporting non-atomic migrations in 
> >Django. 
> > 
> >Database transactions are always wrapped in transactions (on DBs that 
> >support transactional DDL like Postgres). Generally this is a good 
> >idea. 
> > 
> >However, one can't do batched updates in data migrations which is 
> >essential 
> >for performing changes on big tables on a live DB [1]. It's also not 
> >possible to create indexes concurrently on Postgres from inside a 
> >transaction. 
> > 
> >Therefore, I'd like to have support for non-atomic migrations in Django 
> > 
> >because it's pretty messy to work around not having proper support for 
> >that 
> >[2]. 
> > 
> >Here's a proof-of-concept implementation [3] of exempting specific 
> >migrations from being wrapped in a transaction by setting `atomic = 
> >False` 
> >on the migration: 
> > 
> >
> https://github.com/django/django/compare/master...Ableton:non-atomic-migrations
>  
> > 
> >Do you agree that non-atomic migrations should be supported by Django? 
> > 
> >Is setting an `atomic` property on a migration a good API for that? 
> > 
> >If there's a chance this will be merged, I'd add documentation, 
> >incorporate 
> >your feedback, and open a ticket or PR. 
> > 
> >Thanks, 
> >Ludwig 
> > 
> >[1] http://pankrat.github.io/2015/django-migrations-without-downtimes/ 
> >[2] 
> >
> http://stackoverflow.com/questions/31247810/commit-manually-in-django-data-migration
>  
> >[3] 
> >
> https://github.com/django/django/compare/master...Ableton:non-atomic-migrations
>  
>
>

-- 
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 it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/d3668bf1-1783-47f8-80f8-c6a33752eace%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can you remove a model's last field of SQLite3 in Django 1.8?

2015-11-29 Thread Baptiste Mispelon 

Hi,

I believe the issue you're describing has already been reported: 
https://code.djangoproject.com/ticket/24424



This ticket is still open and there is a long discussion on it (30 
comments).



Baptiste

On 11/29/2015 06:15 PM, KwangYoun Jung wrote:

Can you remove a model's last field of SQLite3 in Django 1.8?

I have a model that has only one column in SQLite3.
When I remove a last field of the model, I get an error like below

*django.db.utils.OperationalError: near ")": syntax error

*Anyone knows about this issue ?
--
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 it, send 
an email to django-developers+unsubscr...@googlegroups.com 
.
To post to this group, send email to 
django-developers@googlegroups.com 
.

Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/2e536e7e-c342-4d6b-b53c-5d08386a861c%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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 it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/565B347F.5030606%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Can you remove a model's last field of SQLite3 in Django 1.8?

2015-11-29 Thread KwangYoun Jung 
Can you remove a model's last field of SQLite3 in Django 1.8?

I have a model that has only one column in SQLite3.
When I remove a last field of the model, I get an error like below



*django.db.utils.OperationalError: near ")": syntax error*Anyone knows 
about this issue ?

-- 
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 it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/2e536e7e-c342-4d6b-b53c-5d08386a861c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Integrating Django with Tornado's web server

2015-11-29 Thread Asif Saifuddin 
Hi,

I used django-websocket-redis for implementing webscet in django project.

You could try that.

Regards

Asif

On Monday, September 14, 2009 at 3:30:59 AM UTC+7, Bret Taylor wrote:
>
> I am one of the authors of Tornado (http://www.tornadoweb.org/), the 
> web server/framework we built at FriendFeed that we open sourced last 
> week (see http://bret.appspot.com/entry/tornado-web-server). 
>
> I just checked in change to Tornado that enables you to run any WSGI- 
> compatible framework on Tornado's HTTP server so that Django apps 
> could run on top of Tornado's HTTP server and benefit from some of the 
> performance work we have done. (I just sent a message to django-users@ 
> with getting started instructions as well, but if you are interested, 
> take a look at 
> http://github.com/facebook/tornado/blob/master/tornado/wsgi.py#L188). 
>
> I chose the WSGI approach because it is generic and applies to all 
> frameworks, but Django is obviously the most widely used. I am curious 
> if there is any benefit to implementing more "native" support in 
> django.core.handlers or if WSGI is the preferred way of adding support 
> for new servers. If there is any performance or usability benefit, let 
> me know, because we would be happy to contribute our time to make it 
> happen. 
>
> In the meantime, if you find any issues with our WSGI support, let me 
> know so we can fix problems. 
>
> Bret 
>

-- 
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 it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/84486ed5-ee46-42d1-8925-e1d9ff7984e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.