[DiscordArchive] example?
[DiscordArchive] example?
Original source
Example?
rektbyfaith
11-09-2020, 07:35 PM #1Archived author: Foe • Posted: 2024-01-06T14:08:14.184000+00:00
Original source
Example?
Original source
semantic aspect hs been very neglected in wow emu sadly
rektbyfaith
11-09-2020, 07:35 PM #2Archived author: Barbz • Posted: 2020-11-09T19:35:45.105000+00:00
Original source
semantic aspect hs been very neglected in wow emu sadly
Original source
basically just means instead of calling tables directly using procedures get/set data. That way the procedures can do whatever they need to with the call. That way the underlying database structure can change without affecting the application
rektbyfaith
11-09-2020, 07:37 PM #3Archived author: DrtyByt • Posted: 2020-11-09T19:37:54.877000+00:00
Original source
basically just means instead of calling tables directly using procedures get/set data. That way the procedures can do whatever they need to with the call. That way the underlying database structure can change without affecting the application
Original source
give a concrete example, it'd be better
but these kind of refactor are rarely put in action by our volunteers devs ^^
rektbyfaith
11-09-2020, 09:51 PM #4Archived author: Barbz • Posted: 2020-11-09T21:51:40.098000+00:00
Original source
give a concrete example, it'd be better
but these kind of refactor are rarely put in action by our volunteers devs ^^
Original source
so instead of having the application have a SQL command it uses like "Select guid, name from acore_characters Where id = ?"
It gets replaced with something like sp_GetAccountCharacters in the DB (a stored procedure). The app then calls sp_GetAccountCharacters(?) with the ? being the id of the account.
This is a very simple example, but it lets you separate out the app vs db code easier because if theres a change and a table gets split or merged, or structural changes happen then the app is insulated. Also most db engines can create a cached plan of the procedure and it runs faster than doing direct sql calls.
rektbyfaith
11-10-2020, 12:00 AM #5Archived author: DrtyByt • Posted: 2020-11-10T00:00:46.212000+00:00
Original source
so instead of having the application have a SQL command it uses like "Select guid, name from acore_characters Where id = ?"
It gets replaced with something like sp_GetAccountCharacters in the DB (a stored procedure). The app then calls sp_GetAccountCharacters(?) with the ? being the id of the account.
This is a very simple example, but it lets you separate out the app vs db code easier because if theres a change and a table gets split or merged, or structural changes happen then the app is insulated. Also most db engines can create a cached plan of the procedure and it runs faster than doing direct sql calls.
Original source
cache for chars? no
rektbyfaith
11-10-2020, 12:02 AM #6Archived author: DandyPlays • Posted: 2020-11-10T00:02:02.344000+00:00
Original source
cache for chars? no
Original source
for world its a nice idea
but for chars, there r to much update/select querys
rektbyfaith
11-10-2020, 12:02 AM #7Archived author: DandyPlays • Posted: 2020-11-10T00:02:25.473000+00:00
Original source
for world its a nice idea
but for chars, there r to much update/select querys
Original source
you'd create procedures for all access paths you need
rektbyfaith
11-10-2020, 12:20 AM #8Archived author: DrtyByt • Posted: 2020-11-10T00:20:56.950000+00:00
Original source
you'd create procedures for all access paths you need
1 Guest(s)
1 Guest(s)