Renaming user model
I'm following the guide provided in this answer, but I've run into an issue. I'm renaming myauth.MyUser
to myauth.User
.
I created my first set of migrations from other apps, converting every ForeignKey to an IntegerField. The migrations were created fine.
I then changed the name or my User model and created a migration, this was also fine.
I created my third set of migrations changing the fields back to ForeignKeys to the new model. These migrations also created fine.
I then manually added dependencies to the migration files, so that the FK -> Int migrations required the previous version of the user app, and the Int -> FK migrations required the latest, renaming migration.
All seems fine, however when I try to run manage.py migrate, I get the following error (a lot of times - for each FK):
The field otherapp.Model.user was declared with a lazy reference to 'myauth.user', but app 'myauth' doesn't provide model 'user'.
What is going on? Is there a way out of this situation?
django database-migration
add a comment |
I'm following the guide provided in this answer, but I've run into an issue. I'm renaming myauth.MyUser
to myauth.User
.
I created my first set of migrations from other apps, converting every ForeignKey to an IntegerField. The migrations were created fine.
I then changed the name or my User model and created a migration, this was also fine.
I created my third set of migrations changing the fields back to ForeignKeys to the new model. These migrations also created fine.
I then manually added dependencies to the migration files, so that the FK -> Int migrations required the previous version of the user app, and the Int -> FK migrations required the latest, renaming migration.
All seems fine, however when I try to run manage.py migrate, I get the following error (a lot of times - for each FK):
The field otherapp.Model.user was declared with a lazy reference to 'myauth.user', but app 'myauth' doesn't provide model 'user'.
What is going on? Is there a way out of this situation?
django database-migration
Sounds like you putmyapp.user
instead ofmyapp.User
in your FK definitions.
– Daniel Roseman
Nov 22 '18 at 10:32
@DanielRoseman, nope the models.py files are correct, and the migrations generated successfully (they wouldn't have if I'd misdeclared).
– user31415629
Nov 22 '18 at 11:34
add a comment |
I'm following the guide provided in this answer, but I've run into an issue. I'm renaming myauth.MyUser
to myauth.User
.
I created my first set of migrations from other apps, converting every ForeignKey to an IntegerField. The migrations were created fine.
I then changed the name or my User model and created a migration, this was also fine.
I created my third set of migrations changing the fields back to ForeignKeys to the new model. These migrations also created fine.
I then manually added dependencies to the migration files, so that the FK -> Int migrations required the previous version of the user app, and the Int -> FK migrations required the latest, renaming migration.
All seems fine, however when I try to run manage.py migrate, I get the following error (a lot of times - for each FK):
The field otherapp.Model.user was declared with a lazy reference to 'myauth.user', but app 'myauth' doesn't provide model 'user'.
What is going on? Is there a way out of this situation?
django database-migration
I'm following the guide provided in this answer, but I've run into an issue. I'm renaming myauth.MyUser
to myauth.User
.
I created my first set of migrations from other apps, converting every ForeignKey to an IntegerField. The migrations were created fine.
I then changed the name or my User model and created a migration, this was also fine.
I created my third set of migrations changing the fields back to ForeignKeys to the new model. These migrations also created fine.
I then manually added dependencies to the migration files, so that the FK -> Int migrations required the previous version of the user app, and the Int -> FK migrations required the latest, renaming migration.
All seems fine, however when I try to run manage.py migrate, I get the following error (a lot of times - for each FK):
The field otherapp.Model.user was declared with a lazy reference to 'myauth.user', but app 'myauth' doesn't provide model 'user'.
What is going on? Is there a way out of this situation?
django database-migration
django database-migration
asked Nov 22 '18 at 10:20
user31415629user31415629
449214
449214
Sounds like you putmyapp.user
instead ofmyapp.User
in your FK definitions.
– Daniel Roseman
Nov 22 '18 at 10:32
@DanielRoseman, nope the models.py files are correct, and the migrations generated successfully (they wouldn't have if I'd misdeclared).
– user31415629
Nov 22 '18 at 11:34
add a comment |
Sounds like you putmyapp.user
instead ofmyapp.User
in your FK definitions.
– Daniel Roseman
Nov 22 '18 at 10:32
@DanielRoseman, nope the models.py files are correct, and the migrations generated successfully (they wouldn't have if I'd misdeclared).
– user31415629
Nov 22 '18 at 11:34
Sounds like you put
myapp.user
instead of myapp.User
in your FK definitions.– Daniel Roseman
Nov 22 '18 at 10:32
Sounds like you put
myapp.user
instead of myapp.User
in your FK definitions.– Daniel Roseman
Nov 22 '18 at 10:32
@DanielRoseman, nope the models.py files are correct, and the migrations generated successfully (they wouldn't have if I'd misdeclared).
– user31415629
Nov 22 '18 at 11:34
@DanielRoseman, nope the models.py files are correct, and the migrations generated successfully (they wouldn't have if I'd misdeclared).
– user31415629
Nov 22 '18 at 11:34
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428705%2frenaming-user-model%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428705%2frenaming-user-model%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Sounds like you put
myapp.user
instead ofmyapp.User
in your FK definitions.– Daniel Roseman
Nov 22 '18 at 10:32
@DanielRoseman, nope the models.py files are correct, and the migrations generated successfully (they wouldn't have if I'd misdeclared).
– user31415629
Nov 22 '18 at 11:34