[DiscordArchive] You guys aware of any ways to actually view the code for data insertion into DB ? Is this strictly
[DiscordArchive] You guys aware of any ways to actually view the code for data insertion into DB ? Is this strictly
Original source
well most of emulator code isnt rly good maybe thats why
rektbyfaith
03-29-2024, 01:39 PM #31Archived author: Rymercyble • Posted: 2024-03-29T13:39:10.471000+00:00
Original source
well most of emulator code isnt rly good maybe thats why
Original source
An ORM would add useless overhead at runtime.
Everytime you add a high level library you loose perf.
Besides like <@218402627636035585> says, most data is loaded at emulator startup.
DB is only used for persistence after... And all possible prepared statements are referenced
rektbyfaith
03-29-2024, 01:42 PM #32Archived author: Elmsroth • Posted: 2024-03-29T13:42:39.007000+00:00
Original source
An ORM would add useless overhead at runtime.
Everytime you add a high level library you loose perf.
Besides like <@218402627636035585> says, most data is loaded at emulator startup.
DB is only used for persistence after... And all possible prepared statements are referenced
Original source
I kind of feel like bean is expecting an API layer at the database rather than direct calls. Or that there is a centralized page in the MVC/code itself that handled all of the calls to the DB. Rather than inline SQL calls.
rektbyfaith
03-29-2024, 02:09 PM #33Archived author: Abillister • Posted: 2024-03-29T14:09:46.284000+00:00
Original source
I kind of feel like bean is expecting an API layer at the database rather than direct calls. Or that there is a centralized page in the MVC/code itself that handled all of the calls to the DB. Rather than inline SQL calls.
Original source
Which would make intercepting/reviewing all of the calls simpler. But would require that main DB call page to be able to handle each type of interaction.
rektbyfaith
03-29-2024, 02:10 PM #34Archived author: Abillister • Posted: 2024-03-29T14:10:23.588000+00:00
Original source
Which would make intercepting/reviewing all of the calls simpler. But would require that main DB call page to be able to handle each type of interaction.
Original source
Thats what I would do in node but what do I know about C
rektbyfaith
03-29-2024, 03:18 PM #35Archived author: Bean • Posted: 2024-03-29T15:18:32.476000+00:00
Original source
Thats what I would do in node but what do I know about C
Original source
From my limited understanding that is realistically the architecture goal that MVC had (though include pages already were designed to handle this as well; but it wasn't part of the true architecture). But from my, also limited, experience it can be difficult to maintain - especially as the number of hands involved increases and the number of code reviewers increases/changes.
It takes a lot of discipline to make sure that everyone involved is only adding the DB calls in one 'area' (not necessarily oen page) and cross referencing all of the existing calls to see if there is one that already exists and/or if an existing one should be updated to accomodate vs a new one created.
Next thing you know you have 5 sets of calls that are all doing similar but not quite identical things. Then someone updates 1 to make a specific call and someone else creates a separate one to make the same call...
rektbyfaith
03-29-2024, 03:24 PM #36Archived author: Abillister • Posted: 2024-03-29T15:24:48.483000+00:00
Original source
From my limited understanding that is realistically the architecture goal that MVC had (though include pages already were designed to handle this as well; but it wasn't part of the true architecture). But from my, also limited, experience it can be difficult to maintain - especially as the number of hands involved increases and the number of code reviewers increases/changes.
It takes a lot of discipline to make sure that everyone involved is only adding the DB calls in one 'area' (not necessarily oen page) and cross referencing all of the existing calls to see if there is one that already exists and/or if an existing one should be updated to accomodate vs a new one created.
Next thing you know you have 5 sets of calls that are all doing similar but not quite identical things. Then someone updates 1 to make a specific call and someone else creates a separate one to make the same call...
Original source
I emphasize the limited because I was more of a DBA that used scripting type logic with simple classic ASP or C# pages to create proof of concepts (for the front end, the back end SQL being the main part I designed). Once it was proofed it went to real developers. When I moved to a team that primarily used MVC I struggled to follow the code but constantly found consistency issues with the DB calls (again, troubleshooting more of the 'DB' issues but coming from the code).
So most of my knowledge with MVC was trying to read up on it to better understand. Then getting a headache and hiding in my simple tSQL and relationship data - which I could easily point to all of the connections based upon PK's, FK's, and consistent naming schema.
rektbyfaith
03-29-2024, 03:28 PM #37Archived author: Abillister • Posted: 2024-03-29T15:28:26.610000+00:00
Original source
I emphasize the limited because I was more of a DBA that used scripting type logic with simple classic ASP or C# pages to create proof of concepts (for the front end, the back end SQL being the main part I designed). Once it was proofed it went to real developers. When I moved to a team that primarily used MVC I struggled to follow the code but constantly found consistency issues with the DB calls (again, troubleshooting more of the 'DB' issues but coming from the code).
So most of my knowledge with MVC was trying to read up on it to better understand. Then getting a headache and hiding in my simple tSQL and relationship data - which I could easily point to all of the connections based upon PK's, FK's, and consistent naming schema.
1 Guest(s)
1 Guest(s)