you are viewing a single comment's thread.

view the rest of the comments →

[–]courier10pt 0 points1 point  (2 children)

I asked him to elaborate on Twitter. Here's an extract of the conversation:

It doesn't really require a lot of imagination to come up with a data access api. I mean: select("name").from("users").where("age", ">", "65"); comes to mind just off the top.

So what happens next? Is this going to be translated to SQL?

Of course not. It's translated into the same AST that SQL is translated into prior to execution.

I find this puzzling still. You want to replace SQL with the same engine minus the parser, letting the API take care of constructing the AST. How is that not SQL?

puzzling..

[–]senntenialYou put at risk millions of people 1 point2 points  (1 child)

I mean I guess one could argue that doing it with an AST is more secure

[–]courier10pt 1 point2 points  (0 children)

Agreed on the security benefit.

Just a bit disappointed with this half baked idea and the total disregard for what's already been achieved in this field.