#django

/

      • adw1n has quit
      • ai4pres has quit
      • ai4pres joined the channel
      • amcm
        I see. Yeah, that cascade could be a problem. Not coming up with anything quick to resolve this sadly.
      • ArrSee
        Damn
      • amcm
        http://django-authtools.readthedocs.io/en/lates... <-- look at this? setting db_table on your new User might help quite a bit. Dirty, but your FK's won't have to change to a different table
      • Custom user classes are really best done from the get go. Oi... Just realized I'm going to have to make this transition soon. but I only have 5 users and non-prod. Lots of FK's though.
      • ArrSee
        amcm: Yeah, but I'm trying to go from a proof of concept to an application
      • and I think setting db_table won't change the MigrationHistory error
      • amcm
        ArrSee can you pastebin more of the error. I'll take a look later, gotta run to lunch
      • theology joined the channel
      • ArrSee
      • have a nice meal
      • ConstantineChe has quit
      • mikeliss joined the channel
      • doubitchou joined the channel
      • doubitchou has left the channel
      • FASDFSF has quit
      • laithal has quit
      • ai4pres has quit
      • ai4pres joined the channel
      • ai4pres has quit
      • ai4pres joined the channel
      • JordiGH has left the channel
      • carljm
        kit: did you get any other responses to the question about PEP8ifiying migrations? (sorry, been off IRC for a while, and my irssi backlog doesn't go back that far)
      • (FWIW I'd be in favor, provided it doesn't add a lot of complexity or fragility)
      • bradfordli123 joined the channel
      • amcm
        ArrSee the api and users migrations are both your application?
      • djosh has quit
      • fission6 has quit
      • samsagaz has quit
      • samsagaz joined the channel
      • fpghost84 joined the channel
      • tourdownunder joined the channel
      • ArrSee
        amcm: yes. I've managed to fix the error occurring on the api app, but now I have the same error for the admin app
      • and that's standard Django so i'm not touching those migrations
      • amcm
        +1
      • bradfordli123 has quit
      • only choice there is to un-apply them.
      • bradfordli123 joined the channel
      • ArrSee
        that's what I tried
      • amcm
        So if you change the table name, all your FK's are going to break, you'll need migrations to re-point them at the new table.
      • ArrSee
        on deploy, the first migration I do is a migrate --fake admin zero
      • but that still gives me the error
      • amcm
        So it's probably "best" though a bit dirty to keep the auth_users table name. I'm thinking there's still probably going to be some data dump, drop table, create table import data kinda stuff
      • have to do it with integrity checking off, so the FK's doing cascade or complain about being invalid
      • ArrSee
        I can do a custom migration if necessary to save the data myself
      • amcm
        --fake admin zero... that's clever, didn't work though? If you had your users.0001_initial mirror the current state of the auth.users table, you could fake into that one, then you should be clear to apply the migration that alters to fit your new models
      • ArrSee
        it didn't work, no
      • hmm
      • ellisonleao joined the channel
      • ellisonleao has left the channel
      • ai4pres has quit
      • ai4pres joined the channel
      • jaykay joined the channel
      • ellisonleao joined the channel
      • ellisonleao has left the channel
      • amcm: Do you know where I can find the standard Django user or the auth migrations?
      • john2x has quit
      • amcm
        in site-package django/contrib/auth/migrations (guessing)
      • should be around there
      • ArrSee
        yup, I found it on github
      • thanks
      • brunch875 has quit
      • brunch875 joined the channel
      • b00tstr4p joined the channel
      • LondonAppDev has quit
      • mikeliss has quit
      • OtherAllan joined the channel
      • fission6 joined the channel
      • djosh joined the channel
      • geek joined the channel
      • geek
        I am not sure if I would create an ERP system in gtk or in django :( I am undecided because I don't know django's true power
      • v0lksman
        I'm making one in Django right now
      • ai4pres has quit
      • ArrSee
        amcm: that didn't work either
      • samsagaz has quit
      • amcm
        drat.
      • MavJS
        geek: best way to find out is to build it with that exact thing you don't know the true power of ;)
      • ai4pres joined the channel
      • Leeds has quit
      • the_rat has quit