| From: | Dann Corbit <DCorbit(at)connx(dot)com> |
|---|---|
| To: | 'Carlos Mennens' <carlos(dot)mennens(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: NoSQL -vs- SQL |
| Date: | 2010-10-12 00:42:01 |
| Message-ID: | 87F42982BF2B434F831FCEF4C45FC33E4203A846@EXCHANGE.corporate.connx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-
> owner(at)postgresql(dot)org] On Behalf Of Carlos Mennens
> Sent: Monday, October 11, 2010 4:47 PM
> To: pgsql-general(at)postgresql(dot)org
> Subject: [GENERAL] NoSQL -vs- SQL
>
> Just wondering how you guys feel about NoSQL and I just wanted to
> share the following article...
>
> http://www.linuxjournal.com/article/10770
>
> Looking to read your feedback and / or opinions.
NoSQL is ideal for situations where we have a single table with no children.
Consider something like FACEBOOK or the like, where there is a unique id for a single table, and there are jillions of records.
We just want to find, insert, update or delete this entry and it has no parents or children.
A simple key/store database is all that is needed.
That is where the NoSQL model shines.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2010-10-12 01:50:02 | Re: NoSQL -vs- SQL |
| Previous Message | Darren Duncan | 2010-10-12 00:27:56 | Re: NoSQL -vs- SQL |