zlacker

[return to "Google's new pipe syntax in SQL"]
1. yarg+lT9[view] [source] 2024-08-28 22:40:15
>>heyden+(OP)
This reminds me .NET's short lived Linq to SQL;

There was a talk at the time, but I can't find the video: http://jaoo.dk/aarhus2007/presentation/Using+LINQ+to+SQL+to+....

Basically, it was a way to cleanly plug SQL queries into C# code.

It used this sort of ordering (where the constraints come after the thing being constrained); it needed to do so for IntelliSense to work.

◧◩
2. dragon+eU9[view] [source] 2024-08-28 22:49:01
>>yarg+lT9
> This reminds me .NET's short lived Linq to SQL;

"Short lived"? Its still alive, AFAIK, and the more popular newer thing for the same use case, Linq to Enntities, has the same salient features but (because it is tied to Entity Framework and not SQL Server specific) is more broadly usable.

◧◩◪
3. yarg+YW9[view] [source] 2024-08-28 23:14:47
>>dragon+eU9
It was in 3.5 only.

If they've replaced it with something else in the last decade and a half that does not mean that they didn't get rid of it, or that it wasn't short lived.

https://learn.microsoft.com/en-us/dotnet/framework/data/adon...

◧◩◪◨
4. LeonB+2Y9[view] [source] 2024-08-28 23:25:37
>>yarg+YW9
Yeh. Linq to sql was a much more lightweight extension than EF, and was killed due to internal warring at MS.

Database people were investing a lot of time and energy on doing things “properly” with EF, and this scrappy little useful tool, linq to sql, was seen as a competitor.

[go to top]