Maybe I've been doing database development for too long, but aren't you better off using a stored procedure? Embedding SQL doesn't make sense for most applications.
Sometimes you need to dynamically generate SQL in the application, but I don't think this solves that problem.
Maybe this will make a lot more sense after I get a good look at Yukon? I don't see much value for the client or the middle tier, but maybe on the database server itself.
Clearly there's some value in the idea - catching problems at runtime is no fun.