[Tutorial] Why Dini is bad to use
#8

Quote:
Originally Posted by [uL]Pottus
View Post
This should really read "Just use MySQL/SQLite" to me the difference between INI and MySQL/SQLite is a cheap wine compared to an expensive wine. It just feels like INI these days is something I used when I didn't know any better
That's true, going to add that section right now .

EDIT: Although, this is solely a tutorial about how awful the dini library is, I'll add a SQL section just for the sake of completing the tutorial.

I'll also link to Konstantinos' SQLite tutorial and a threaded MySQL tutorial so I don't have to write a whole section about it.

Quote:
Originally Posted by Sublime
View Post
What if the file used for reading is real huge? Won't that double the space if .part were to be there?
In reality, yes, but only for a few milliseconds at most, since the .part file is deleted shortly thereafter.

dini just opens the original file and writes the contents into the .part file. The original file is then deleted and the .part file is renamed to the original file's name.
Reply


Messages In This Thread
Why Dini shouldn't be used - by Emmet_ - 21.11.2013, 14:40
Re: Why Dini is bad to use - by Tamer - 21.11.2013, 14:45
Re: Why Dini is bad to use - by Patrick - 21.11.2013, 14:48
Re: Why Dini is bad to use - by Sublime - 21.11.2013, 14:51
Re: Why Dini is bad to use - by Emmet_ - 21.11.2013, 15:04
Re: Why Dini is bad to use - by Pottus - 21.11.2013, 15:35
Re: Why Dini is bad to use - by Sublime - 21.11.2013, 15:36
Re: Why Dini is bad to use - by Emmet_ - 21.11.2013, 15:57
Re: Why Dini is bad to use - by Pottus - 21.11.2013, 16:20
Re: Why Dini is bad to use - by Emmet_ - 21.11.2013, 16:32

Forum Jump:


Users browsing this thread: 3 Guest(s)