Re: Turn off migrations completely in Django 1.7

Hi, We've been hitting this issue as well in our environment - so far we've been able to workaround this by using fake migrations but that is not long lasting solution. We're using Oracle as our database backend and we have hundreds of legacy databases which aren't unified at their schema

Re: Turn off migrations completely in Django 1.7

Perhaps giving some actionable, constructive feedback would be more useful. On Tuesday, August 1, 2017 at 6:50:47 PM UTC-4, Robert F. wrote: > > I know this is an old topic but I completely agree with Frank. Nothing > gives me more headaches and makes me want to move off Django more than >

Re: Turn off migrations completely in Django 1.7

I know this is an old topic but I completely agree with Frank. Nothing gives me more headaches and makes me want to move off Django more than migrations. They seldom run smoothly and cause me no end of headaches. I hate them! On Friday, November 20, 2015 at 2:26:59 PM UTC-8, Frank Malina

Re: Turn off migrations completely in Django 1.7

On 22 April 2016 at 02:02, wrote: > Yeah, good call perhaps. We're certainly drawn to raw sql (which we all > know fairly well) compared to learning Django's tricks for complex queries, > but the originator of our project chose to write lots of unit tests using > sqlite

Re: Turn off migrations completely in Django 1.7

On Thursday, 21 April 2016 18:51:48 UTC+10, Marcin Nowak wrote: > > If you're building some report-like queries, or any static queries, I > would suggest to use raw sql. > You can optionally wrap results with model instances using > Model.objects.raw(). > Thanks Marcin. Yeah, good call

Re: Turn off migrations completely in Django 1.7

On 21 April 2016 at 10:06, wrote: > Either way - we recently hit another Django limitation - as best I've been > able to tell, joining a table with itself seems to be very poorly supported > - so we're heading towards SqlAlchemy, and probably away from Django > altogether

Re: Turn off migrations completely in Django 1.7

Thanks for the comment Matt. I wasn't trying to change anything in the database, it was just that Django wanted the django_migrations table to exist, but it didn't, and the db was read-only for safety during testing. Could well be that I wasn't using fake properly, I'm not sure, but I'd

Re: Turn off migrations completely in Django 1.7

On Wednesday, December 2, 2015 at 6:31:31 PM UTC+10:30, john@gmail.com wrote: > > +1 for disabling migrations completely - for several reasons. > > 1. Right now, I'm trying to run tests against a production database with > runserver, in *read-only* mode - but it fails because it can't

Re: Turn off migrations completely in Django 1.7

On Wednesday, August 26, 2015 at 1:08:51 PM UTC+2, grzegorz.stalmierski wrote: > > > With current architecture around migrations Django > is database owner, not one of the database services. > > Application layer is chaning over time and its lifetime is a way shorter than database and data.

Re: Turn off migrations completely in Django 1.7

+1 for disabling migrations completely - for several reasons. 1. Right now, I'm trying to run tests against a production database with runserver, in *read-only* mode - but it fails because it can't create the django_migrations table. (I'm in the process of upgrading from Django 1.4 to 1.8, so

Re: Turn off migrations completely in Django 1.7

Just unsubscribe from the list, and then subscribe again with the desired email. On 11/20/2015 5:15:07 PM, d...@gearscape.net wrote: On 2015-11-20 16:37, Frank Malina wrote: > RE: Carl Meyer >>> To my knowledge, out of the many hundreds of >>> thousands of Django users, you

Re: Turn off migrations completely in Django 1.7

On 2015-11-20 16:37, Frank Malina wrote: RE: Carl Meyer To my knowledge, out of the many hundreds of thousands of Django users, you are the first and only one to request a way to turn off migrations entirely. No he isn't, Django migrations are ridiculous waste of time, never work and make

Re: Turn off migrations completely in Django 1.7

RE: Carl Meyer >> To my knowledge, out of the many hundreds of >> thousands of Django users, you are the first and only one to request a >> way to turn off migrations entirely. No he isn't, Django migrations are ridiculous waste of time, never work and make me angry. I work with Django from

Re: Turn off migrations completely in Django 1.7

On 26 August 2015 at 16:50, Carl Meyer wrote: > At this point the discussion belongs on the django-developers list, to > enumerate the real-world use cases and sort out the pros and cons of the > various possibilities. Getting a change into Django is rarely > impossible, but it

Re: Turn off migrations completely in Django 1.7

2015-08-26 16:15 GMT+02:00 Carl Meyer : > You quoted me out of context. ​I'm sorry. It was unintentional. ​ -- ​Regards, ​Greg Stalmierski.​ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group

Re: Turn off migrations completely in Django 1.7

On 08/26/2015 08:15 AM, Carl Meyer wrote: > I agree, and I already suggested a new feature (`managed=False` at the > AppConfig level) for which I think a solid patch would most likely be > accepted. This new feature would be capable of handling the "don't > migrate anything" case as well as the

Re: Turn off migrations completely in Django 1.7

Hi Grzegorz, > On Aug 26, 2015, at 2:25 AM, Grzegorz Stalmierski > wrote: > > W dniu 25.08.2015 o 19:04, Marcin Nowak pisze: >> >> I would like to provide solid patch as a pull request, but I'm afraid that >> it will be rejected due to some kind of spirit,

Re: Turn off migrations completely in Django 1.7

On Tue, Aug 25, 2015 at 5:27 PM, Carl Meyer wrote: > To my knowledge, out of the many hundreds of > thousands of Django users, you are the first and only one to request a > way to turn off migrations entirely. > I think that's a little unfair, given that migrations are only in

Re: Turn off migrations completely in Django 1.7

W dniu 25.08.2015 o 19:04, Marcin Nowak pisze: I would like to provide solid patch as a pull request, but I'm afraid that it will be rejected due to some kind of spirit, politics or something else. BR, Marcin Marcin, please - consider sharing your patch on GitHub (or similar) with a

Re: Turn off migrations completely in Django 1.7

On 25 August 2015 at 18:44, Marcos Eliziario wrote: Changing the database accidentally can be avoided simply by adjusting the > privileges of the database user django uses. It's not perfect. The connection requires write access and Django inserts some data

Re: Turn off migrations completely in Django 1.7

Changing the database accidentally can be avoided simply by adjusting the privileges of the database user django uses. Flexibility in a software project always come out at the expense of simplicity. So, generally, django developers are right to avoid rarely need features in exchange for a

Re: Turn off migrations completely in Django 1.7

On 25 August 2015 at 17:04, Carl Meyer wrote: > Hmm, yes, third-party apps are an issue. > > My recollection from the last time you brought this up is that we > decided an AppConfig-level setting to do the equivalent of managed=False > for an entire app would be a reasonable

Re: Turn off migrations completely in Django 1.7

> > Maybe there is a solution for both? > > Sometimes when you have unusual requirements you have to do a little > more work to meet them. To my knowledge, out of the many hundreds of > thousands of Django users, you are the first and only one to request a > way to turn off migrations entirely.

Re: Turn off migrations completely in Django 1.7

On 08/25/2015 09:23 AM, Marcin Nowak wrote: > On 25 August 2015 at 17:04, Carl Meyer > wrote: > > Hmm, yes, third-party apps are an issue. > > My recollection from the last time you brought this up is that we > decided an AppConfig-level

Re: Turn off migrations completely in Django 1.7

On 08/25/2015 09:02 AM, Marcin Nowak wrote: > > On 25 August 2015 at 16:53, Carl Meyer > wrote: > > I thought we already covered this topic, and `managed=False` should work > for your use case. That's the exact meaning of this flag: "I don't

Re: Turn off migrations completely in Django 1.7

On 25 August 2015 at 16:53, Carl Meyer wrote: > I thought we already covered this topic, and `managed=False` should work > for your use case. That's the exact meaning of this flag: "I don't want > Django to manage my database, please never touch it." Have you tried > adding

Re: Turn off migrations completely in Django 1.7

On 08/25/2015 08:42 AM, Marcin Nowak wrote: > > On 25 August 2015 at 16:21, Tim Graham > wrote: > > What does "turning off migrations" mean in practice? Is it not > enough to avoid the makemigrations and migrate management commands? >

Re: Turn off migrations completely in Django 1.7

On 25 August 2015 at 16:21, Tim Graham wrote: > What does "turning off migrations" mean in practice? Is it not enough to > avoid the makemigrations and migrate management commands? Currently I'm replacing mgmt commands to avoid accidential calls, and also replacing test

Re: Turn off migrations completely in Django 1.7

What does "turning off migrations" mean in practice? Is it not enough to avoid the makemigrations and migrate management commands? On Tuesday, August 25, 2015 at 9:31:30 AM UTC-4, bobhaugen wrote: > > I agree that migrations should be optional, for all the reasons listed in > this thread, but

Re: Turn off migrations completely in Django 1.7

I agree that migrations should be optional, for all the reasons listed in this thread, but hope it doesn't now turn into a religious war between models-first and database-first. Not relevant to the issue. > > -- You received this message because you are subscribed to the Google Groups

Re: Turn off migrations completely in Django 1.7

On 25 August 2015 at 14:32, Avraham Serour wrote: > > We're working with databases and their representations in application > layer, and not vice versa. > > Speak for yourself, I'm working with the models, saving them in the > database is just an implementation detail > I'm

Re: Turn off migrations completely in Django 1.7

> We're working with databases and their representations in application layer, and not vice versa. Speak for yourself, I'm working with the models, saving them in the database is just an implementation detail On Tue, Aug 25, 2015 at 3:21 PM, wrote: > > > On Tuesday,

Re: Turn off migrations completely in Django 1.7

On Tuesday, April 28, 2015 at 7:20:17 AM UTC+2, Mike Dewhirst wrote: > > Anyway, I suspect disabling migration - even if a > "master-switch" could be built - is undesirable if one is using any of > the django tables. > > > I'm not sure we're talking about the same. Some of us don't need

Re: Turn off migrations completely in Django 1.7

Jamie Well I agree top-posting is usually a problem - especially for those who hate it. But in this case the top-poster was semi-hijacking the thread and in doing so felt the need to top post to differentiate the subject matter. That difference was in "disabling migrations" versus turning off

Re: Turn off migrations completely in Django 1.7

On Apr 27, 2015, at 7:01 PM, Mike Dewhirst wrote: > >> On 27/04/2015 9:54 AM, marcin.j.no...@gmail.com wrote: >> So what about that? I'm also interested in disabling migrations. > > Would it suffice to have all your models specify "managed = False" in the > Meta class? >

Re: Turn off migrations completely in Django 1.7

On 27/04/2015 9:54 AM, marcin.j.no...@gmail.com wrote: So what about that? I'm also interested in disabling migrations. I need to upgrade Django in big project (from 1.4 to newer version) because of lack of support for 1.4, but migrations included in v1.7 will complicate this process. Would it

Re: Turn off migrations completely in Django 1.7

So what about that? I'm also interested in disabling migrations. I need to upgrade Django in big project (from 1.4 to newer version) because of lack of support for 1.4, but migrations included in v1.7 will complicate this process. I want to disable everything related to migrations. We're

Re: Turn off migrations completely in Django 1.7

Hmm, the problem is that there doesn't appear to be any way to turn off the creation of the migrations table itself, even if all of the other models are set to managed=False as suggested by Nikolas. I've commented it out for now but it would be ideal to have some way of turning it off

Re: Turn off migrations completely in Django 1.7

You could always set your models to managed=False https://docs.djangoproject.com/en/dev/ref/models/options/#managed _Nik On 9/18/2014 2:04 PM, Anthony Tuininga wrote: Hi, I just upgraded my test environment to Django 1.7 and immediately noticed that mgirations appear to be a requirement.

Re: Turn off migrations completely in Django 1.7

Hi, I feel your pain, but I think you can utilize something with --fake I have been using databases for many, many years, and honestly- migrations definitely make sense. I am able to add new fields within a few seconds without having to do any extra work. It takes 2 minutes to learn how to use

Turn off migrations completely in Django 1.7

Hi, I just upgraded my test environment to Django 1.7 and immediately noticed that mgirations appear to be a requirement. Searching the documentation and the code itself seems to indicate that there is no way to disable it, either. Did I miss something? I don't need or want Django to create or