How to change primary key generation to api tokens

[satheler]

I am usually using uuid as the primary key in all tables and I want to define this in API tokens table.
Is there any way to change the primary key value from increment integer to uuid values generated?

[miqbalrr]

you only need the primary key as uuid in Tokens table or all?
why you change that? i thought the tokens table is executed by adonis system too

[satheler]

I already managed to change the tables that I want to use the uuid. But to standardize my entire project I would also like to change this setting in the Tokens table.
The problem is not with the migration part, but with the model, I would have to change the id to string, for example.

[thetutlage]

If you will change the primary key to uuid then it will increase the token size massively, since the id is encoded within the generated token for faster lookups.

Technically uuid and auto increment counters both should work. Its just that they will impact the overall size of the token

[thetutlage]

Which version of the framework you are using? v4.1 or v5

[satheler]

v5

[thetutlage]

In v5, we do not create any model for the API tokens. Can you share the code that you are talking about?

[satheler]

Currently, this is the database builder to insert a api token
insert into `api_tokens` (`created_at`, `expires_at`, `name`, `token`, `type`, `user_id`) values (?, ?, ?, ?, ?, ?)

but I would like that
insert into `api_tokens` (`id` ,`created_at`, `expires_at`, `name`, `token`, `type`, `user_id`) values (?, ?, ?, ?, ?, ?, ?)

Note: where I can provide the id value instead of database auto increment. This value would a uuid, for example.

A suggestion for make that:
New options as optional in authConfig inside provider key (config/auth.ts)

/*
|--------------------------------------------------------------------------
| UUID as Identifier Key Value
|--------------------------------------------------------------------------
|
| The UUID as Identifier Key Value use uuid generated value instead of auto increment provided by database
|
*/
uuidAsIdentifierKeyValue?: boolean

And make a instruction to change database migration
table.increments('id').primary() to table.uuid('id').primary()

[thetutlage]

Got it. I have to think a bit about a better way to allow this (no answers for now). Also why don't you rely on the database to generate the uuid for you? If using PostgreSQL it has extensions for doing same.