+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Coding (https://hackforums.net/forumdisplay.php?fid=151)
+---- Forum: Web Development (https://hackforums.net/forumdisplay.php?fid=183)
+---- Thread: [PHP] NoSQL: Pure PHP DataBase System Class V0-BETA (/showthread.php?tid=4648084)
Pages: Pages
1
2
* - clickosface - Jan 28, 2015
tLooks very good. Well done.
tanks ty
* - Ego Inc - Jan 28, 2015
(Jan 28, 2015 12:19 PM)clickosface Wrote: tLooks very good. Well done.
tanks ty
Naw it's shit. Much better version coming soon tho.
* - 3mmi - Jan 29, 2015
So far so good mate. Keep up the good work, this is interesting.
* - ShadowCloud - Jan 29, 2015
Firstly, this is a really valiant attempt at something that's actually extremely complex. Whether this works or not, I applaud you for actually putting your head down and getting into it.
Haxalot has provided some really good feedback and I absolutely read it as constructive feedback, I can only hope you do as well ;)
That being said, here's my concerns for using this:
The one thing you absolutely have to find a way around is a locking mechanism for flat files. You are bound to have concurrency issues if you don't address this directly. How will you handle deadlock conditions and/or dirty reads?
Caching mechanisms will be vital so you can read frequently accessed data from a cache, preferably keeping small pieces in memory?
Have you considered some form of indexing to speed up retrieving specific data?
I'd like to have a way to fetch a list of rows rather than only being able to fetch a row with a specific ID. In most cases I won't know the ID either... I'm getting a pastebin removed message from the OP, so I can't see if you have a function for this?
How are you handling the load of existing items? If I have 2GB of data, is this being initialized when I create an instance of the DB?
Again, overall you have a long way to go, but this is way better than what I expected when I saw the thread title. Good job ;)
* - Support Operator - Jan 29, 2015
You should store all the data in JSON rather than a new file per row etc. Also, you shouldn't read the file each time a lookup is done... you should store it in a variable and then as the __destroy() method; save it.
Other than that, good idea... not the best execution.