[DiscordArchive] How it'll work Is you have a list of saved sets in a json per texture. when scanning you can save th
[DiscordArchive] How it'll work Is you have a list of saved sets in a json per texture. when scanning you can save th
Original source
How it'll work Is you have a list of saved sets in a json per texture. when scanning you can save that set.?
rektbyfaith
01-30-2024, 05:52 PM #1Archived author: Titi • Posted: 2024-01-30T17:52:34.955000+00:00
Original source
How it'll work Is you have a list of saved sets in a json per texture. when scanning you can save that set.?
Original source
It won't save the IDs. It will save the settings. When fetching that set we either try to find an existing entry with the settings or create a new one, like blizz
rektbyfaith
01-30-2024, 05:53 PM #2Archived author: Titi • Posted: 2024-01-30T17:53:55.640000+00:00
Original source
It won't save the IDs. It will save the settings. When fetching that set we either try to find an existing entry with the settings or create a new one, like blizz
Original source
Probably just lazy. Cause they use SQL as main storage. So searching for duplicates should not be hard
rektbyfaith
01-30-2024, 05:56 PM #3Archived author: Deamon • Posted: 2024-01-30T17:56:21.024000+00:00
Original source
Probably just lazy. Cause they use SQL as main storage. So searching for duplicates should not be hard
Original source
Noggit should also use sql instead of local jsons for team work
rektbyfaith
01-30-2024, 05:58 PM #4Archived author: Titi • Posted: 2024-01-30T17:58:21.236000+00:00
Original source
Noggit should also use sql instead of local jsons for team work
Original source
the duplicates isn't the key, you have to compare every single column values
rektbyfaith
01-30-2024, 06:01 PM #5Archived author: Titi • Posted: 2024-01-30T18:01:57.829000+00:00
Original source
the duplicates isn't the key, you have to compare every single column values
Original source
So? Non-unique indexes over each field will make search pretty fast even in relational DB
rektbyfaith
01-30-2024, 06:02 PM #6Archived author: Deamon • Posted: 2024-01-30T18:02:39.828000+00:00
Original source
So? Non-unique indexes over each field will make search pretty fast even in relational DB
Original source
Blizz use Oracle DB for storing all this data. So it should not be an issue
rektbyfaith
01-30-2024, 06:03 PM #7Archived author: Deamon • Posted: 2024-01-30T18:03:11.194000+00:00
Original source
Blizz use Oracle DB for storing all this data. So it should not be an issue
Original source
My most wanted feature. Amazing.
UI can always be improved later. It's actually very hard to determine most convenient UI beforehand. It becomes more clear after playing with it.
rektbyfaith
01-30-2024, 06:40 PM #8Archived author: Jagulars • Posted: 2024-01-30T18:40:49.528000+00:00
Original source
My most wanted feature. Amazing.
UI can always be improved later. It's actually very hard to determine most convenient UI beforehand. It becomes more clear after playing with it.
1 Guest(s)
1 Guest(s)