Database vs In Mod Storage

[ArielT]

So, which would be more efficient for storing/accessing 2DA information if I wanted to preload 2DAs?

A) Store the 2da in a table in an SQL database
-or-
B) Store the 2da on a way point object in the module

[Disco]

Depends on what you exactly want to do, I'd say. I wouldn't store the whole spell.2da on a waypoint.

Since 1.6x 2da caching has become less of a bottleneck, as far as I know. We (Amia) just let the engine do the work. I do cache things like ban lists and who is a DM on waypoints, though. Those things are in the database but don't change often enough to warrant a full db query for every login, as far as I am concerned.

[Terra_777]

Getting data from a 2da is much faster then getting the 500th+ local variable entry off an object.
_________________
I dun have any signature, I'm happy anyway.

[ShaDoOoW]

if your datas got more then one column, 2da or database is your friend, both for efficiency and scripting simplicity

then if you want search in those datas, database is your friend, if not 2da is enough
_________________
Community Patch / NWNX Patch / NWNX Files / NWNX Connect

[Tenshar]

This may sound noobish, but how do you store something on a waypoint? I don't have SQL and my host doesn't want me to use it so i have no experience with MySQL at all. can you only store 2das on waypoints or can you store other stuff like integers?
If you can store integers on them, do they stay on it after reset?
Thx

-Tenshar

[ShaDoOoW]

Okay.

1) make new empty location and create waypoint with tag "2DA_spells" there
2) add this script into your OnModuleLoad event:

[Tenshar]

Thx, I got another question though,
If an integer is stored on a placeable or waypoint or something by a player, will the integer still be there after a server reset?

[Baaleos]

Things on placeables, local vars etc, get wiped at a server reset, because the object is essentially destroyed.

If you were to store the placeable in a local campagin database, that would store all the vars on it, but that goes back to file reading and writing operations, which are slow.

[virusman]

SCO/RCO don't work on placeables.
_________________
In Soviet Russia, NWN plays you!

[Baaleos]

ah

K - Then no.... there is no way to save local vars without database storage.
Must be on a creature or item. Lol

[ShaDoOoW]

[Baaleos]

True, the 2da data is stored securely on your waypoint, but its not writeable/saveable, it will always be at the state it was in toolset..

Its a purely read only storage.

If however, the waypoint, was swapped out with a creature instead, then it could be read/writable, because you could have it set to store all of its 2da's in a database every 10 minutes or something - or just when it has its data changed.

Then on mod load, it restores the 'fresh' data.


But as you say... for what he needs, it would work perfectly.

[Tenshar]

[Baaleos]

Yes... but they will do that on a waypoint too anyway.


What im pointing out is 2 things.


1. Waypoints cannot be stored into databases, which means that you wont be able to update the data that is stored on them, and save it, so that the new data is there when you reset the module.

2. Creatures however, can be stored into databases, meaning that the data stored on them, can be updated, and then saved between resets.


But in the case of your waypoint system, it is storing 2da strings, which are not likely to change, which therefore would not require you to make it possible to update and save the data beyond a reset.


If you open the module in toolset, you will see that the waypoint will have the 2da strings on it as variables, these are stored permanently to that placeable, unless removed.

Everytime you restart the module, that waypoint will be restored to this 'state'.


My suggestion about using creatures, was just in the event that you wanted to update the data.
eg - Add some additional 2da string values, without having to go through the process of saving a game, move the sav file to module folder, rename, toolset, export etc....


But for what you want this to do, storing 2da data statically on a waypoint, the method posted above, will work perfectly for what you require, no need to use creatures, although creatures would work just as well.

[Tenshar]

Actually, I do want the data to be updated because, when players use a specific tool it saves their public CD-Key on a placeable, and when the rest, die or log on it checks if theyre public cd key is on that npc and if it is it applies certain effects to then, this stays after relogging but not after a reset, so If I use an NPC instead of a placeable it should save the data and stay there after a reset right?