Comments on: Cleaning up with JSON and SQL in Django http://www.davidcramer.net/code/448/cleaning-up-with-json-and-sql.html A blog about Django, JavaScript, CSS, and general web development. Tue, 09 Mar 2010 21:59:12 -0600 http://wordpress.org/?v=2.9.2 hourly 1 By: David http://www.davidcramer.net/code/448/cleaning-up-with-json-and-sql.html/comment-page-1#comment-20781 David Wed, 22 Apr 2009 19:06:27 +0000 http://www.davidcramer.net/?p=448#comment-20781 @ashwoods The only downside to things like couchdb is (last I looked) they haven't been proven. I'd love to use a non-relational database but there's really no great solution out there yet. @ashwoods The only downside to things like couchdb is (last I looked) they haven’t been proven. I’d love to use a non-relational database but there’s really no great solution out there yet.

]]> By: ashwoods http://www.davidcramer.net/code/448/cleaning-up-with-json-and-sql.html/comment-page-1#comment-20780 ashwoods Wed, 22 Apr 2009 13:59:50 +0000 http://www.davidcramer.net/?p=448#comment-20780 Wouldn't a document-based database make more sense? I am currently working on a custom django field that doesnt store the data in the database, "redirects" to a couchdb entry. Wouldn’t a document-based database make more sense?
I am currently working on a custom django field that doesnt store the data in the database, “redirects” to a couchdb entry.

]]> By: igorekk http://www.davidcramer.net/code/448/cleaning-up-with-json-and-sql.html/comment-page-1#comment-20770 igorekk Thu, 16 Apr 2009 08:05:30 +0000 http://www.davidcramer.net/?p=448#comment-20770 Peter, Yes, siteconfig app is great and very useful :) Peter, Yes, siteconfig app is great and very useful :)

]]> By: Peter http://www.davidcramer.net/code/448/cleaning-up-with-json-and-sql.html/comment-page-1#comment-20769 Peter Wed, 15 Apr 2009 20:12:19 +0000 http://www.davidcramer.net/?p=448#comment-20769 The djblets projects has a similar field called JSONField. It is also used in their siteconfig app (which works great for my needs). The djblets projects has a similar field called JSONField. It is also used in their siteconfig app (which works great for my needs).

]]> By: Henning http://www.davidcramer.net/code/448/cleaning-up-with-json-and-sql.html/comment-page-1#comment-20768 Henning Wed, 15 Apr 2009 19:15:00 +0000 http://www.davidcramer.net/?p=448#comment-20768 A good use case for JSON fields are user preferences in my opinion. A good use case for JSON fields are user preferences in my opinion.

]]> By: David http://www.davidcramer.net/code/448/cleaning-up-with-json-and-sql.html/comment-page-1#comment-20767 David Wed, 15 Apr 2009 17:34:55 +0000 http://www.davidcramer.net/?p=448#comment-20767 Yep I can give you two great examples: 1) Lifestream We store custom data based on each extension, in one table. The extension then decides how to handle this data. It's a smart denormalization. 2) iBegin We have way too many rows and an alter requires downtime. This metadata doesn't change often, but it's just that, metadata. If we need to build indexes on it we can do that in another fashion. It's much more efficient using it out of a JSONField rather than doing more SQL queries for a set of key/value pairs. Yep I can give you two great examples:

1) Lifestream

We store custom data based on each extension, in one table. The extension then decides how to handle this data. It’s a smart denormalization.

2) iBegin

We have way too many rows and an alter requires downtime. This metadata doesn’t change often, but it’s just that, metadata. If we need to build indexes on it we can do that in another fashion.

It’s much more efficient using it out of a JSONField rather than doing more SQL queries for a set of key/value pairs.

]]> By: sharms http://www.davidcramer.net/code/448/cleaning-up-with-json-and-sql.html/comment-page-1#comment-20766 sharms Wed, 15 Apr 2009 17:25:19 +0000 http://www.davidcramer.net/?p=448#comment-20766 I can attest that in the real world frequently there are requests for '1 more field' or frequently unused data types that may only exist on a few objects. Traditional database design doesn't fit well in many scenarios. I can attest that in the real world frequently there are requests for ‘1 more field’ or frequently unused data types that may only exist on a few objects.

Traditional database design doesn’t fit well in many scenarios.

]]> By: amccloud http://www.davidcramer.net/code/448/cleaning-up-with-json-and-sql.html/comment-page-1#comment-20764 amccloud Wed, 15 Apr 2009 13:53:23 +0000 http://www.davidcramer.net/?p=448#comment-20764 @Andy Baker Because it is a ridiculously large dataset. The schema doesn't keep changing, just different records store a little bit of extra custom data. @Andy Baker

Because it is a ridiculously large dataset. The schema doesn’t keep changing, just different records store a little bit of extra custom data.

]]> By: Andy Baker http://www.davidcramer.net/code/448/cleaning-up-with-json-and-sql.html/comment-page-1#comment-20763 Andy Baker Wed, 15 Apr 2009 11:52:12 +0000 http://www.davidcramer.net/?p=448#comment-20763 I'm having a trouble imagining a use-case here. If your schema does change that often how about a table for key/value pairs or something like that? Why does your schema keep changing? Is there a better way to model the data that might avoid the problem? I’m having a trouble imagining a use-case here.

If your schema does change that often how about a table for key/value pairs or something like that?

Why does your schema keep changing? Is there a better way to model the data that might avoid the problem?

]]>