BUY Lasix (Brand) ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/?utm_source=rss&utm_medium=rss&utm_campaign=design-documents-in-couchdb-and-validation Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 BUY Lasix (Brand) ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/comment-page-1/#comment-48021 Jan Van Ryswyck Thu, 30 Jul 2009 19:25:24 +0000 http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/#comment-48021 @dm: Thx for the suggestion. I've already picked up some of the noice about other document DBs, including mongodb. Interesting to hear about "collections" - indeed a very interesting feature. Being new to document databases in general, I'll definitely have a look at mongodb as well. @dm: Thx for the suggestion. I’ve already picked up some of the noice about other document DBs, including mongodb. Interesting to hear about “collections” – indeed a very interesting feature. Being new to document databases in general, I’ll definitely have a look at mongodb as well.

]]> BUY Lasix (Brand) ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/comment-page-1/#comment-48008 dm Thu, 30 Jul 2009 12:00:33 +0000 http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/#comment-48008 Personally I am a fan of keeping the concept of tables ("collections") around for JSON-style stores. In MongoDB, which like Couch is document-oriented, there is the concept of collections - one would have an orders collection and customers collection. I still find that model useful when I write db apps. It is still schemaless in the sense that the objects in the collections can have any desired fields -- for example one could just have a "things" collection there and dump everything in it as above. One nice side effect is that objects of the same "type" are grouped together physically on disk which can be good for performance in certain circumstances too; I guess in theory CouchDB could do this internally by being very smart. p.s I am a committer on mongodb and have my biases...check both out for yourself, right tool for the right job. Personally I am a fan of keeping the concept of tables (“collections”) around for JSON-style stores. In MongoDB, which like Couch is document-oriented, there is the concept of collections – one would have an orders collection and customers collection. I still find that model useful when I write db apps. It is still schemaless in the sense that the objects in the collections can have any desired fields — for example one could just have a “things” collection there and dump everything in it as above. One nice side effect is that objects of the same “type” are grouped together physically on disk which can be good for performance in certain circumstances too; I guess in theory CouchDB could do this internally by being very smart.

p.s I am a committer on mongodb and have my biases…check both out for yourself, right tool for the right job.

]]> BUY Lasix (Brand) ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/comment-page-1/#comment-47981 Ray Daly: Learning CouchDB by Ray Daly Tue, 28 Jul 2009 14:23:16 +0000 http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/#comment-47981 [...] in CouchDB July 10, 2009 * [http://elegantcode.com/2009/07/10/views-into-couchdb/ ] July 10, 2009 * Design Documents in CouchDB and Validation July 18, [...] [...] in CouchDB July 10, 2009 * [http://elegantcode.com/2009/07/10/views-into-couchdb/ ] July 10, 2009 * Design Documents in CouchDB and Validation July 18, [...]

]]> BUY Lasix (Brand) ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/comment-page-1/#comment-47850 Jan Thu, 23 Jul 2009 10:25:27 +0000 http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/#comment-47850 I guess it's a style question. I prefer function(doc) { if(doc.type == "foo") { emit(doc.key, doc.value); } } over the return. plus, leaving out curly braces is plain evil :) I guess it’s a style question. I prefer

function(doc) {
if(doc.type == “foo”) {
emit(doc.key, doc.value);
}
}

over the return. plus, leaving out curly braces is plain evil :)

]]> BUY Lasix (Brand) ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/comment-page-1/#comment-47793 Dew Drop – July 20, 2009 | Alvin Ashcraft's Morning Dew Mon, 20 Jul 2009 12:10:34 +0000 http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/#comment-47793 [...] Design Documents in CouchDB and Validation and NHibernate 2.1 and Collection Event Listeners (Jan Van Ryswyck) [...] [...] Design Documents in CouchDB and Validation and NHibernate 2.1 and Collection Event Listeners (Jan Van Ryswyck) [...]

]]> BUY Lasix (Brand) ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/comment-page-1/#comment-47777 Daily Links for Sunday, July 19th, 2009 Sun, 19 Jul 2009 11:35:06 +0000 http://elegantcode.com/2009/07/18/design-documents-in-couchdb-and-validation/#comment-47777 [...] Design Documents in CouchDB and Validation | Elegant Code [...] [...] Design Documents in CouchDB and Validation | Elegant Code [...]

]]>