03.06.2020, 06:52
Are you experiencing performance trouble doing it this way? I'd say that having tables for each system separately and updating them when needed is a better idea, and is safer when it comes to facing errors, since one system or two would get affected, not the entire saving system.
I'd say, lesser queries = lesser requests and may slightly be better on your performance but you should consider maintaining well-structured queries when you are considering performance, keeping queries organized according to what they are being used for is better in my opinion.
I see some people consider using one big query is better but since you're using pawn in your case, you need to create a very big string if you want to use one query, and you will eventually need to split up this query so it wouldn't do a difference any more, you will mostly end up doing it how you do it now. Except that you will waste time and effort.
I always recommend having stuff organized, and sometimes it might not be the best for performance, but it's worth it.
I'd say, lesser queries = lesser requests and may slightly be better on your performance but you should consider maintaining well-structured queries when you are considering performance, keeping queries organized according to what they are being used for is better in my opinion.
I see some people consider using one big query is better but since you're using pawn in your case, you need to create a very big string if you want to use one query, and you will eventually need to split up this query so it wouldn't do a difference any more, you will mostly end up doing it how you do it now. Except that you will waste time and effort.
I always recommend having stuff organized, and sometimes it might not be the best for performance, but it's worth it.