Good vs. Evil

[lenscas]

98 @Someone Else 37 well, it currently creates prepared statements due to me using luaDBI. However I will have to drop that sooner or later and replace it with luaSQL due to it not updating. Luasql doesn't support prepared statements and I thus need to escape everything instead. Which is less secure I think.

 

[RealKC]

99 ...<that's a reason

 

[erindalc]

100 Good. Reset.

 

[RealKC]

49 evil needs to win

 

[erindalc]

48 Fine

 

[RealKC]

47 awesome

 

[erindalc]

46 yep

 

[RealKC]

45 down

 

[erindalc]

44 Okay

 

[RealKC]

43 I need to go to sleep, bye!

 

[erindalc]

42 Good night

 

[Someone Else 37]

43 Wow, the count's been falling fast...

 

[Your mom]

43. Ew no, I hate following crowds! :3

 

[duckfan77]

42 WHO BE YOU

 

[erindalc]

41 BURN THE HERETIC

 

[lenscas]

42 and suddenly lua is being annoying.
./lcCore/database.lua:72: bad argument #2 to 'print' (expected table to have __tostring metamethod)


edit:41

 

[Your mom]

42why do people have to be so evil

 

[lenscas]

42 and I fixed the problem which let me to find the above thing (which isn't much of a problem as you probably don't need a tostring on a table anyway)
But then I thaught about the fact that a update probably needs some more escaping then just the values used in the where thus need to rewrite some things but this looks promising
UPDATE users
SETid = 2 , name = LOLZ
WHERE id = ?
THIS IS ONLY HERE TO CAUSE A CRASH <! WHERE AWEOMSECheck the sql syntax.

(missing space is already fixed)

 

[erindalc]

42 BECAUSE WE MUST GO DOWN

 

[lenscas]

41 because

errors,message=sth:execute(unpack(self.values),unpack(self.arguments))

won't work.
(Having said that, there might be a syntax for it to get it to work but....meh I have another work around already)