To get your UUID's bytes, you'll want to see what methods are provided by the language your application is written in. There also don't seem to be any functions available for converting to and from a formatted UUID string. So there are no UUID-specific column types or storage classes. After that, a column's declared type isn't used. When SQLite creates a table, it uses a column's declared type to determine which of the five underlying storage classes (integer, real, text, blob or null) it will use. And since a UUID is just a 128-bit integer, you could also store the integer's bytes as a BLOB, which I imagine would be slightly faster.īut to more directly answer what I believe is the question at hand, no, SQLite does not have any features that directly support UUID's. So you could store the UUID in the formatted, human-readable string format and make that your table's key. But to more directly answer what I believe is the question at hand, no, SQLite does not have any features that directly support UUIDs. This value is used in the INSERT statement. As mentioned, a column (or multiple columns) of any type can be used as a primary key. In this example, a randomly generated UUID is fetched using the randomuuid function. In this example we will create a UUID field for postgresql (which has a. CL's answer is correct but kind of skirts the issue at hand. In this example were using SqliteDatabase, but you could also use one of the.
0 kommentar(er)
