Simple data storage

/54/3d/310002/1.html

I have a hud that tracks distance travelled.
I want one of the HUDs option to store that distance in a file(?).
I want to manipulate that data and store it as such:

NAME OF OWNER
TOTAL DISTANCE TRAVELLED TO DATE
DISTANCE TRAVELLED THIS JOURNEY

I currently send this information to an external database and use PHP to do all the work but I think it would be more efficient if I kept it internal to the HUD.

I have looked at the link above for ideas but would like to get your input or a simple code clip. thanks

I should mention that I am guessing only 1 row is required as this information is only for that one owner. And its only a few fields, each being updated after every journey. For example

1st Journey:
______________________
Owner Name : Joe Doe
Distance Traveled this Journey : 320
Total Distance Traveled to Date: 320
______________________

2nd Journey


______________________
Owner Name : Joe Doe
Distance Traveled this Journey : 4000
Total Distance Traveled to Date: 4320
______________________

If you already have the data elements defined for export, then you have 90% of the work finished already. Since you've already discovered Very's system, you have the other 10% mostly in hand also.

If you want to do your own scripting, this project doesn't sound like it's too challenging. LSL is not designed well for data storage... certainly not for the sort of database manipulation and report generation that other languages are great at. Whatever you do internally is going to feel clunky compared to what you can do with PHP and SQL on a server that is meant to handle lots of data. Still, so long as you don't overload your script's memory a project like this is not hard in LSL. You can store your three data per record as elements in a strided list and then read them back out in sets of three when you want to generate a report. Take a look at the discussion of strided lists at http://lslwiki.net/lslwiki/wakka.php?wakka=list.

Another option to strided lists is just using multiple lists, in your case three, as this can be more memory efficient for larger result sets, but will be more complicated if you want to sort them somehow.

But it also has the added advantage of being able to use llListStatistics() to more quickly total a column if you wish.

great thanks. I think I will stick with sending it to an external db and manage it via php

just store the info in a prim's DESCRIPTION field and use a seperator character between the values. then all you need to do is parse that string back into your variables, adjust them and then at journey's end, write them back.