[DiscordArchive] how it is right now it just goes through the table and returns the tickets with the players guid rig
[DiscordArchive] how it is right now it just goes through the table and returns the tickets with the players guid rig
Original source
You could just cache all that data on startup/reload
rektbyfaith
01-12-2023, 01:10 AM #51Archived author: Foe • Posted: 2023-01-12T01:10:07.383000+00:00
Original source
You could just cache all that data on startup/reload
Original source
No real reason to load it on player login unless you worry about memory cost, which I wouldn't
rektbyfaith
01-12-2023, 01:10 AM #52Archived author: Foe • Posted: 2023-01-12T01:10:26.382000+00:00
Original source
No real reason to load it on player login unless you worry about memory cost, which I wouldn't
Original source
ah ok
rektbyfaith
01-12-2023, 01:10 AM #53Archived author: Crow • Posted: 2023-01-12T01:10:34.657000+00:00
Original source
ah ok
Original source
As new tickets are created you load it into your cache and then you could push it later or async update it
rektbyfaith
01-12-2023, 01:10 AM #54Archived author: Nix • Posted: 2023-01-12T01:10:34.939000+00:00
Original source
As new tickets are created you load it into your cache and then you could push it later or async update it
Original source
When you want to remove tickets if you use the table structure I recommended, you just remover the PlayerGuid entry from the first table
rektbyfaith
01-12-2023, 01:10 AM #55Archived author: Nix • Posted: 2023-01-12T01:10:54.681000+00:00
Original source
When you want to remove tickets if you use the table structure I recommended, you just remover the PlayerGuid entry from the first table
Original source
I'd just async update it as well as update your in memory cache
rektbyfaith
01-12-2023, 01:11 AM #56Archived author: Foe • Posted: 2023-01-12T01:11:05.588000+00:00
Original source
I'd just async update it as well as update your in memory cache
Original source
No need to iterate through the tickets, however this also means you'd need to reload the data on login, so the question is whether or not you have the ram (you should) to simply leave it in memory
rektbyfaith
01-12-2023, 01:11 AM #57Archived author: Nix • Posted: 2023-01-12T01:11:11.500000+00:00
Original source
No need to iterate through the tickets, however this also means you'd need to reload the data on login, so the question is whether or not you have the ram (you should) to simply leave it in memory
Original source
The tickets won't change between logins unless you do direct database changes, but perhaps instead of that you could implement ingame commands to modify existing tickets either by deleting or changing them which can then be properly reflected in the cache and pushed async to the DB
rektbyfaith
01-12-2023, 01:11 AM #58Archived author: Nix • Posted: 2023-01-12T01:11:56.621000+00:00
Original source
The tickets won't change between logins unless you do direct database changes, but perhaps instead of that you could implement ingame commands to modify existing tickets either by deleting or changing them which can then be properly reflected in the cache and pushed async to the DB
Original source
gonna sound stupid but what do you mean by memory cache and updating syncs
rektbyfaith
01-12-2023, 01:12 AM #59Archived author: Crow • Posted: 2023-01-12T01:12:26.143000+00:00
Original source
gonna sound stupid but what do you mean by memory cache and updating syncs
Original source
Your memory cache is your lua table
rektbyfaith
01-12-2023, 01:12 AM #60Archived author: Nix • Posted: 2023-01-12T01:12:33.716000+00:00
Original source
Your memory cache is your lua table
1 Guest(s)
1 Guest(s)