.NET 클라이언트 라이브러리를 사용한 강력하게 입력된 뷰

그리고 latest bits of the Couchbase .NET Client Library support a few different view querying options.  In this post, I'll describe those options in detail.  To play along at home, make sure you have the latest Couchbase Server installed with the beer-sample sample bucket. 

I've added a view named “by_name” to the beer-sample bucket in the “beer” design doc.  This view simply creates a secondary index on the “name” property of “beer” documents.

Querying this view with the non-generics version of GetView will yield an enumerable collection of IViewRow instances which contain information about the rows in the view.

Setup your client code as follows:

Then query the view:

The IViewRow interface defines properties for the “id” and “key” properties in the row and additionally provides a dictionary with access to each property in the row. 

If you wanted to retrieve the original documents associated with each of the rows, you would take the row.ItemId and query using the client's Get 메서드를 사용합니다.

Alternatively, you could do a multi-get to retrieve all documents in one call. Note that with this version, the view is queried when the LINQ 선택 method is called, as opposed to above when the enumeration of view queries the view.  In either case, it's the enumeration of the IView instance that triggers the request to the view on the server.

Now, let's say you have a 맥주 class in your application and you want to get instances of 맥주s when you iterate over the view. 

The Beer class makes use of Newtonsoft.Json for serializing and deserializing JSON.  The client library also has a dependency on this assembly.

With the new 맥주 class, it's possible to query the view and tell the client that 맥주 instances should be the item returned by each enumeration of a row in the view.

Two important changes to note in the snippet above.  First, when GetView is called, 맥주 is specified as the generic type.  Second, the third argument supplied to GetView tells the client to Get the original document and deserialize it to an instance of T or in this case, a 맥주.

In the case where the value returned by a row is a projection of the indexed document, then strongly typed views are still possible. 

Since the view now includes the beer name and style (this is an admittedly contrived use of projections) it is possible to strongly type the view query results – in this case to a BeerProjection 클래스. 

Removing the Boolean argument from the GetView call leaves the default of false and the client will then attempt to deserialize the value property of each view row into an instance of T, or in this case a BeerProjection.

Finally, if you wanted to perform a generic multi-get and use your own deserialization techniques, you could do something like the following: