Skip to main content

C# Learning: Design goals and origins of LINQ

It’s important to know clearly what Microsoft set out to achieve with LINQ.LINQ ships with implementations that support querying against regular object collections, databases, entities, and XML sources.
Because LINQ supports rich extensibility, developers can also easily integrate it
with other data sources and providers.

Another essential feature of LINQ is that it is strongly typed. This means the

■ We get compile-time checking for all queries. Unlike SQL statements today,
where we typically only find out at runtime if something is wrong, this
means we can check during development that our code is correct. The
direct benefit is a reduction of the number of problems discovered late in
production. Most of the time, issues come from human factors. Strongly
typed queries allow us to detect early typos and other mistakes made by the
developer in charge of the keyboard.

■ We get IntelliSense within Visual Studio when writing LINQ queries. This
not only makes typing faster, but also makes it much easier to work against
both simple and complex collection and data source object models.


Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.

Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…