[DiscordArchive] yeah it isn't a large difference, it's just why put it in both places, when i already need to start
[DiscordArchive] yeah it isn't a large difference, it's just why put it in both places, when i already need to start
Archived author: Titi • Posted: 2025-09-23T22:47:24.221000+00:00
Original source
there's a sweet spot around 2000-3000 rows for bulk operations (based on column count) then it is gradually slower because there's too much data to parse
Archived author: tester • Posted: 2025-09-23T22:47:34.535000+00:00
Original source
i mean it isn't really patching dbcs, its read all of the dbc into a map, then modify, then write dbc, but i understand the sentiment
Archived author: tester • Posted: 2025-09-23T22:48:11.775000+00:00
Original source
my real issue is i need to optimize some of the current sql stuff, especially around creatures/items, its the largest time spent on a few modules i got
Archived author: Titi • Posted: 2025-09-23T22:48:37.147000+00:00
Original source
anyways (other than for ts-wow) you should be working on your DBCs in sql
Archived author: tester • Posted: 2025-09-23T22:48:57.101000+00:00
Original source
yes for just generic modding, a sql table is easier to work with
Archived author: Titi • Posted: 2025-09-23T22:49:03.966000+00:00
Original source
whether you use the emulators database tables or separate ones is personal choice
Archived author: Titi • Posted: 2025-09-23T22:49:36.438000+00:00
Original source
and if you use the emulator's, you could disable dbc file reading