- Joined
- Dec 26, 2013
- Messages
- 2,124
- Solutions
- 14
- Reaction score
- 1,518
- Location
- USA
- GitHub
- Codinablack
Didn't think about it that way...but I believe sending a SQL Qeury is probably more efficient than opening a file and reading it.
@Syntax I would have to say that those were more pro's towards sql rather than con's towards lua, but I guess it's the same thing in reality. I suppose I really should do more digging into sql in general, because I was just about to ask you again what is NoSql, and so I googled it, and there are many of different sql services out there. That would be what I need to do more research on I suppose... Thanks for showing me these things...
Thank you to everyone on this thread, I wasn't searching for a definitive answer to a question I didn't ask, didn't find one either. LMAO! If any of that makes any sense, but I was really trying to see the advantages and disadvantages of both languages, and you guys have helped to show me some of them, didn't realize sql could be so powerful, definitely hadn't seen that before, time to try some alternates...
To keep the topic going just a little longer, curiosity has me, what would be some things you guys would say should be used for one and then for the other? I mean like summs example, yeah obviously we don't want to store a quest id in the database, but thinking on a bigger scale, like the pet system. Lets use that for example, who thinks the pet system should be written like zbizu says he is going to do for sql, or like the others were working on in lua? Granted the system is still going to be written in lua, but I mean the data that is stored, for a system like that...