Data File

that’s because i forgot my test server has magic quotes enabled…

thanks for telling me

can I also point out, that you are not buying a comments system, so breaking the page and telling me I need to do more work on it is not that helpful.

the data is read from the file when you first create the object, $data = new data_file(‘something’); and only written to the file when you call the commit method.

all the other functions just work with the array which is kept in memory.

I have tested it with 1000 entries in the comments example and it still performs the same as with 10 entries in terms of speed. This test was done on my local server which never has a load average about 0.02 so I’m not sure how this will translate to a real world test.

Ill post some speed test results now actually, probably worth advertising that in some cases its faster than mysql anyway.

Definitely. I’ve always been a advocate of grabbing data and manipulating it server-side anyway. A relevant suggestion might be to create some cool “select” methods, to really compete with database queries. Especially stuff like grouping, min/max, etc. Just a thought….

thinking about it, you could store an array of data and they use the php array_* functions to do most of the things that mysql allows.

I guess that would make it easy to implement too,

thanks for purchasing, hope you like it.

to remove the last two elements from the array, one being empty and one being the current folder.

take that section of code and put it into a new file and experiment with commenting one array_pop and you should see the difference.

unfortunately array_pop will not take an argument of how many elements to remove from the end of the array so it has to be called twice, that got on my nerves at the time I wrote it too.

The whole point of that section of code is to give me a full base path to work from, to make it more portable,

it does everything described in the documentation,

http://jacekk.co.uk/code/data_file/docs/class.data_file.html

because the system works mostly with arrays, and they are so easy to manipulate with PHP anyway I left it at the documented methods.

what further functionality are you looking for ?, I’m always open to suggestions and ideas for improvement.

the sql example shows how you could store settings in a file for a mysql connection.

The reason I didn’t implement the select methods similar to sql, is that the system works with arrays which are quite easy to manipulate with php anyway, however this has been suggested a few times now so I will look into it.

are there any specific sql-like method you can think of,

at the moment im thinking of adding a select() function that will do some query like tasks, but id like to hear some other ideas.

it should always be faster, when you first open the file all of the data is transferred to a php array (in memory) so SELECTS are basically getting a key from that array, very speedy

Its probably not a good idea to store huge amounts in the file, because you will run out of memory available to php eventually, that’s why I recommend you split the data into as many files as possible.

you can just do

unset($comments[1]);

when you loop over the array you can do

foreach ($array as $index => $post){
   echo $post['email'];
}

inside that loop $index will hold the value of the current array element being used, so you could use that to add a delete link to your posts

foreach ($array as $index => $post){
   echo '<a href="?rm=', $index, '">Delete</a>';
}

then you can check for the $_GET[‘rm’] variable and remove the key its related to. Obviously you would have to make this available to only admins in some way, and stop it being used to just remove all of the posts.

Is that any help ?

You know, I have no idea haha. I never actually bought anything from this site. It doesn’t seem that obvious.

Your intention to give a good rating will do

I wasnt planning on it, but you can store pretty muchy anything, the user info example could be

$user_db = new data_file('user_info.dat');

// to store user info.
$user_db->add($username, array(/* an array of data to store */));

// to get it back
$user_db->get($username);

// this will return the array that was stored previously.

If you are only making one change you can call commit() after add(), if you are making lots it should be called after all of them.

thanks for trying, I think i’ll stick with localStorage as js is more my thing.