<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<div class="moz-text-html" lang="x-unicode"> One simple answer: The
drivers do not work appropriately with complex SQL data types. In
PHP or node.js I will get a string that I have to parse, in
MongoDB, I get a proper object or list. If I used hstore in a
consequent way (I like consequence and unification), I would have
sets in sets, and this is the same as a document oriented
database.<br>
But just intermingling things for fun does not make the world
better.<br>
<span class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Times; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span" style="font-family:
verdana,sans-serif; font-size: 12px; line-height: 18px;
text-align: left;">MongoDB, for example, unifies worlds by
simply using JSON. I don't have to </span></span><span
class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Times; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span" style="font-family:
verdana,sans-serif; font-size: 12px; line-height: 18px;
text-align: left;">manually </span></span><span
class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Times; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span" style="font-family:
verdana,sans-serif; font-size: 12px; line-height: 18px;
text-align: left;">parse things I do not need to parse.</span></span><br>
<br>
Am 19.11.10 09:47, schrieb Sven Geggus:
<blockquote cite="mid:ic5dia$bfv$2@ultimate100.geggus.net"
type="cite">
<pre wrap="">Andreas Kalsch <a class="moz-txt-link-rfc2396E" href="mailto:andreaskalsch@gmx.de"><andreaskalsch@gmx.de></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I think it is not a good idea to use hstore because then we can drop SQL,
use NoSQL for storing data and use PostGIS/Postgres for Geometry only.
</pre>
</blockquote>
<pre wrap="">In the real world there is no black and white! Shure, hstore is comparable
to NoSQL aproaches, but why should it be a bad thing to use a best of both
worlds aproach?
Sven
</pre>
</blockquote>
<br>
</div>
</body>
</html>