Migrating auto generate primary key
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
How can I migrate a primary key field, which was not set to Auto generate before?
From
@PrimaryKey
private int id;
To
@PrimaryKey(autoGenerate=true)
private int id;
Since Sqlite does not support altering columns, my only guess is to migrate the whole table as is and resetting the constraints.
Do I even have to migrate the database during the development process or can I just rebuild it, since my database will change rapidly, so I don't have to migrate every time?
android android-room asked Nov 24 '18 at 9:49
ThePeatThePeat
1
add a comment |
How can I migrate a primary key field, which was not set to Auto generate before?
From
@PrimaryKey
private int id;
To
@PrimaryKey(autoGenerate=true)
private int id;
Since Sqlite does not support altering columns, my only guess is to migrate the whole table as is and resetting the constraints.
Do I even have to migrate the database during the development process or can I just rebuild it, since my database will change rapidly, so I don't have to migrate every time?
android android-room asked Nov 24 '18 at 9:49
ThePeatThePeat
1
add a comment |
How can I migrate a primary key field, which was not set to Auto generate before?
From
@PrimaryKey
private int id;
To
@PrimaryKey(autoGenerate=true)
private int id;
Since Sqlite does not support altering columns, my only guess is to migrate the whole table as is and resetting the constraints.
Do I even have to migrate the database during the development process or can I just rebuild it, since my database will change rapidly, so I don't have to migrate every time?
android android-room asked Nov 24 '18 at 9:49
ThePeatThePeat
1
How can I migrate a primary key field, which was not set to Auto generate before?
From
@PrimaryKey
private int id;
To
@PrimaryKey(autoGenerate=true)
private int id;
Since Sqlite does not support altering columns, my only guess is to migrate the whole table as is and resetting the constraints.
Do I even have to migrate the database during the development process or can I just rebuild it, since my database will change rapidly, so I don't have to migrate every time?
android android-room android android-room asked Nov 24 '18 at 9:49
ThePeatThePeat
1
asked Nov 24 '18 at 9:49
ThePeatThePeat
1
asked Nov 24 '18 at 9:49
ThePeatThePeat
1
asked Nov 24 '18 at 9:49
ThePeatThePeat
1
asked Nov 24 '18 at 9:49
ThePeatThePeat
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I suggest you to change your approach: add an unique identifier (UID) as alternative way to identify records.
You can define a UID with annotation Entity on your POJO.
@Entity(indices={@Index(value="uid", unique=true)})
publi class Pojo {
..
public String uid;
..
}
When you insert a record in your database, you can define uid field using:
String uuid = UUID.randomUUID().toString();
You can use the UUID field to identify your records, in absolute way. When you migrate to a version to another, you don't work with the old ids, you can always work with UID.
answered Nov 26 '18 at 21:06
xcescoxcesco
2,1371734
Thank you for your suggestion, I figured another way a few hours ago :) I located the database via the Device File Explorer in Data > Data > PACKAGENAME > databases > DATABASENAME and could delete it there. Then I started the project again and it rebuilt the database without any errors, this should do the trick during the development process.
– ThePeat
Nov 26 '18 at 21:51
add a comment |
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%2f53456979%2fmigrating-auto-generate-primary-key%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I suggest you to change your approach: add an unique identifier (UID) as alternative way to identify records.
You can define a UID with annotation Entity on your POJO.
@Entity(indices={@Index(value="uid", unique=true)})
publi class Pojo {
..
public String uid;
..
}
When you insert a record in your database, you can define uid field using:
String uuid = UUID.randomUUID().toString();
You can use the UUID field to identify your records, in absolute way. When you migrate to a version to another, you don't work with the old ids, you can always work with UID.
answered Nov 26 '18 at 21:06
xcescoxcesco
2,1371734
Thank you for your suggestion, I figured another way a few hours ago :) I located the database via the Device File Explorer in Data > Data > PACKAGENAME > databases > DATABASENAME and could delete it there. Then I started the project again and it rebuilt the database without any errors, this should do the trick during the development process.
– ThePeat
Nov 26 '18 at 21:51
add a comment |
I suggest you to change your approach: add an unique identifier (UID) as alternative way to identify records.
You can define a UID with annotation Entity on your POJO.
@Entity(indices={@Index(value="uid", unique=true)})
publi class Pojo {
..
public String uid;
..
}
When you insert a record in your database, you can define uid field using:
String uuid = UUID.randomUUID().toString();
You can use the UUID field to identify your records, in absolute way. When you migrate to a version to another, you don't work with the old ids, you can always work with UID.
answered Nov 26 '18 at 21:06
xcescoxcesco
2,1371734
Thank you for your suggestion, I figured another way a few hours ago :) I located the database via the Device File Explorer in Data > Data > PACKAGENAME > databases > DATABASENAME and could delete it there. Then I started the project again and it rebuilt the database without any errors, this should do the trick during the development process.
– ThePeat
Nov 26 '18 at 21:51
add a comment |
I suggest you to change your approach: add an unique identifier (UID) as alternative way to identify records.
You can define a UID with annotation Entity on your POJO.
@Entity(indices={@Index(value="uid", unique=true)})
publi class Pojo {
..
public String uid;
..
}
When you insert a record in your database, you can define uid field using:
String uuid = UUID.randomUUID().toString();
You can use the UUID field to identify your records, in absolute way. When you migrate to a version to another, you don't work with the old ids, you can always work with UID.
answered Nov 26 '18 at 21:06
xcescoxcesco
2,1371734
I suggest you to change your approach: add an unique identifier (UID) as alternative way to identify records.
You can define a UID with annotation Entity on your POJO.
@Entity(indices={@Index(value="uid", unique=true)})
publi class Pojo {
..
public String uid;
..
}
When you insert a record in your database, you can define uid field using:
String uuid = UUID.randomUUID().toString();
You can use the UUID field to identify your records, in absolute way. When you migrate to a version to another, you don't work with the old ids, you can always work with UID.
answered Nov 26 '18 at 21:06
xcescoxcesco
2,1371734
answered Nov 26 '18 at 21:06
xcescoxcesco
2,1371734
answered Nov 26 '18 at 21:06
xcescoxcesco
2,1371734
answered Nov 26 '18 at 21:06
xcescoxcesco
2,1371734
2,1371734
Thank you for your suggestion, I figured another way a few hours ago :) I located the database via the Device File Explorer in Data > Data > PACKAGENAME > databases > DATABASENAME and could delete it there. Then I started the project again and it rebuilt the database without any errors, this should do the trick during the development process.
– ThePeat
Nov 26 '18 at 21:51
add a comment |
Thank you for your suggestion, I figured another way a few hours ago :) I located the database via the Device File Explorer in Data > Data > PACKAGENAME > databases > DATABASENAME and could delete it there. Then I started the project again and it rebuilt the database without any errors, this should do the trick during the development process.
– ThePeat
Nov 26 '18 at 21:51
Thank you for your suggestion, I figured another way a few hours ago :) I located the database via the Device File Explorer in Data > Data > PACKAGENAME > databases > DATABASENAME and could delete it there. Then I started the project again and it rebuilt the database without any errors, this should do the trick during the development process.
– ThePeat
Nov 26 '18 at 21:51
Thank you for your suggestion, I figured another way a few hours ago :) I located the database via the Device File Explorer in Data > Data > PACKAGENAME > databases > DATABASENAME and could delete it there. Then I started the project again and it rebuilt the database without any errors, this should do the trick during the development process.
– ThePeat
Nov 26 '18 at 21:51
add a comment |
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%2f53456979%2fmigrating-auto-generate-primary-key%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
