I also guess that comparing strings on JOINS instead of integer would slow down the database query. What i also need to do is JOINS over 2 - 3 tables. I also guess that when Im using UUID, every time a new database record/entry has been inserted the database needs to reindex the primary key column, since they primary key index is not in a sorted order anymore (which would be when I would use integer auto increment primary key, because every future record is added at the end, because the new auto incremented primary key is always the greatest number so far, so the index will automatically be in sorted order). I guess indexing uuids instead of integers takes longer (comparing string vs. I guess there would be performance issues by using strings (a UUID has 36 characters) as primary key. My question: Is it a bad idea to use a UUID (String / Varchar) as primary key in a android sqlite database table instead of an integer that would be auto incremented? Therefore I need to use something like UUID. So User B will get the changes/updates and can insert/update them into User Bs local device database.īut I need to ensure that the ids of the database entries are unique along the whole system. When User A gets connected to the internet, all changes and new records are delivered to the other collaborative Users. So the User A changes (while he is offline) some data (in ohter words he would update database entries) or add new records to the database. I also want to support offline editing, that are synchronized to the other collaborative users when the user gets connected to the internet. My app needs to get synced with other app users (on there own devices).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |