Pipelines, Filters, Fluent API and LINQ to SQL

UPDATED RELEASE: Initial Release (Apr 11, 2008)

Fri, 11 Apr 2008 08:46:04 GMT

The first time you run the app it will attempt to build the database in the server taken from the connectionstring in the app.config file.

I've selected a generic product tagging mechanism for filtering the data because the two examples given are quite disparate (pg13 and vegetarian). On top of this I am running LINQ to SQL because the deferred execution will allow me to build up a specification of what I want and then "compile" it all into one Transact-SQL statement at the end. The actual filtering process happens in a [url:Pipeline of Filters|http://en.wikipedia.org/wiki/Pipeline_(software)] (although I think I may be leaning more towards a [url:Specification|http://en.wikipedia.org/wiki/Specification_pattern] implementation next if I can figure it out.

Lastly, I have implemented Pagination as a separate concern because I believe that it is a separate concern. Pagination belongs in the UI along with Ordering. Filtering belongs in the Business Logic Layer and the Data Access Layer should just do the CRUD.

I've started to build a fluent interface on top of everything too. This is the first time I've ever done one so it was interesting (harder than I'd thought).

There is more detail in the [url:Blog Post|http://wolfbyte-net.blogspot.com/2008/04/pipe-and-filters-fluent-apis-and-linq.html]

UPDATED RELEASE: Initial Release (Apr 11, 2008)

Fri, 11 Apr 2008 05:57:13 GMT

UPDATED WIKI: Home

michaelminutillo — Fri, 11 Apr 2008 05:46:48 GMT

Resource Page Description
A small sample on building a Pipelines and Filters system on top of LINQ to SQL. A Fluent API is thrown into the mix to make it easier to work with too.

This idea for this stems from a challenge issued by Ayende from his blog. The task is to build a command-line interface for retrieving a list (the first 10) of products from some data-storage mechnsim (up to the implementer) and potentially filter the list using any number of restrictions imposed in any order by passing in parameters to the application.

CREATED RELEASE: Initial Release (Apr 11, 2008)

Fri, 11 Apr 2008 05:37:04 GMT

The first time you run the app it will attempt to build the database in the server taken from the connectionstring in the app.config file.