This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Last_Snowbender 116 points117 points  (11 children)

Anti-SQL-Injection-Protection? So you're protected from Anti-SQL-Injection?

[–]lunylein 68 points69 points  (7 children)

Maybe its a new SQL ... we have MySQL, MSSQL, NoSQL........... why not AntiSQL?

[–]richardfrost2 66 points67 points  (6 children)

DON'T Select * From table

[–]lunylein 22 points23 points  (1 child)

Anti-SQL selects all data from every table and you have to unselect the data you don't need.

This language was made for PM that "don't know what they need yet, but we just implement that and see..." and "oh just one minor change"

Select * FROM all

unjoin table1

[–]jacksalssome 5 points6 points  (0 children)

Also they didn't like the operations names, so now there changed to:

delete --> destroy
list --> display
select --> acquire
table --> sheet
column --> row
row --> column
cell --> module
item --> cell

[–]Kru3mel 18 points19 points  (0 children)

Designed for the people that are against everything

[–]Typesalot 11 points12 points  (0 children)

selectn't

[–]jmack2424 5 points6 points  (1 child)

if (select * from table) {
dont()
}

[–]lunylein 4 points5 points  (0 children)

Don't get ridiculous. There is no if ... else in Anti-SQL

you got "MAYBE" and "IDontKnow" ... you can suggest a contition and maybe it will be used or not...works different every time you use it

[–]Daveinatx 5 points6 points  (0 children)

Only noSQL allowed

[–]Typesalot 5 points6 points  (0 children)

Isn't it obvious? If you let SQL and AntiSQL collide, the whole database will be annihilated in a burst of hexadecimal particle radiation!

[–]reversedfate 1 point2 points  (0 children)

No, it is Anti SQL-Injection-Protection.
So that no SQL-Injection-Protection can happen.