Timeline for Correct organization of the database structure and selection
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2018 at 9:03 | vote | accept | ilw | ||
| Jan 22, 2018 at 9:03 | history | bounty ended | ilw | ||
| Jan 21, 2018 at 17:46 | comment | added | Evan Carroll | @Andreyua not sure, you can certainly use JSON1 on android but I guess it doesn't ship with it. github.com/requery/sqlite-android/tree/master/sqlite-android/… You may consider just storing the properties as JSON for forwards compatibility, seems pretty likely they'll get around to it some day. | |
| Jan 20, 2018 at 8:51 | comment | added | ilw | What about sqlite for android? | |
| Jan 19, 2018 at 19:25 | comment | added | Evan Carroll | @Andreyua SQL Lite should support the above just add JSON1 to it. Much better than using text to describe the properties. | |
| Jan 18, 2018 at 8:59 | comment | added | ilw |
Your answer agrees with my decision. Thank you. But I'm working with sqllite. Perhaps i can do this like: CREATE TABLE task (task_id int GENERATED BY DEFAULT AS IDENTITY, device_id int REFERENCES device, type int, properties text, SequenceNr int); ?
|
|
| Jan 17, 2018 at 16:42 | history | answered | Evan Carroll | CC BY-SA 3.0 |