On Wed, Apr 4, 2012 at 6:26 AM, Josh Berkus j...@agliodbs.com wrote:
While I was doing this I always thought this would have been a better
approach for my previous project, an accounting application. If I could
just have stored entities like invoice customer as a single document
that
On Wed, Apr 4, 2012 at 9:53 AM, Dobes Vandermeer dob...@gmail.com wrote:
I think there is something to be gained by having a first-class concept of a
document in the database. It might save some trouble managing
parent/child relations, versioning, things like that.
Methinks this needs a *lot*
While I was doing this I always thought this would have been a better
approach for my previous project, an accounting application. If I could
just have stored entities like invoice customer as a single document that
is inserted, updated, etc. atomically it would be a lot simpler and faster
On Sat, Mar 31, 2012 at 6:37 AM, Dobes Vandermeer dob...@gmail.com wrote:
On Sat, Mar 31, 2012 at 1:44 AM, Daniel Farina dan...@heroku.com wrote:
On Fri, Mar 30, 2012 at 10:21 AM, Daniel Farina dan...@heroku.com wrote:
Any enhancement here that can't be used with libpq via, say, drop-in
.so
On Sat, Mar 31, 2012 at 1:44 AM, Daniel Farina dan...@heroku.com wrote:
On Fri, Mar 30, 2012 at 10:21 AM, Daniel Farina dan...@heroku.com wrote:
Any enhancement here that can't be used with libpq via, say, drop-in
.so seems unworkable to me, and that's why any solution that is
basically
On Thu, Mar 29, 2012 at 10:55 PM, Dobes Vandermeer dob...@gmail.com wrote:
Virtual hosts. Same port.
In that case, the frontend would not be tied to a specific PostgreSQL
server, then? I think initially this might complicate things a bit, and you
could solve it by putting an HTTP proxy in
On Thu, Mar 29, 2012 at 10:04 AM, Andrew Dunstan and...@dunslane.net wrote:
1. I've been in discussion with some people about adding simple JSON extract
functions. We already have some (i.e. xpath()) for XML.
I've built a couple of applications that push data in and out of xml
via manual
On 03/30/2012 09:57 AM, Merlin Moncure wrote:
What I'm saying is that jsonpath probably isn't the whole story:
another way of bulk moving json into native backend structures without
parsing would also be very helpful. For example, being able to cast a
json document into a record or a record
On Fri, Mar 30, 2012 at 4:30 PM, Daniel Farina dan...@heroku.com wrote:
On Thu, Mar 29, 2012 at 10:55 PM, Dobes Vandermeer dob...@gmail.com
wrote:
Virtual hosts. Same port. I think SPDY or like-protocols [...] give a
crisp treatment to
interactive, stateful workloads involving
On Fri, Mar 30, 2012 at 9:57 PM, Merlin Moncure mmonc...@gmail.com wrote:
On Thu, Mar 29, 2012 at 10:04 AM, Andrew Dunstan and...@dunslane.net
wrote:
1. I've been in discussion with some people about adding simple JSON
extract
functions. We already have some (i.e. xpath()) for XML.
Your
On Fri, Mar 30, 2012 at 10:55 AM, Dobes Vandermeer dob...@gmail.com wrote:
Well, in our case HTTP is a clear win (but not replacement) and SPDY a
potential one (even as a replacement). Even if SPDY is not widely adopted
it could still replace FEBE if there's a clear advantage to using it, I
On 03/30/2012 11:41 AM, Robert Haas wrote:
On Fri, Mar 30, 2012 at 10:55 AM, Dobes Vandermeerdob...@gmail.com wrote:
Well, in our case HTTP is a clear win (but not replacement) and SPDY a
potential one (even as a replacement). Even if SPDY is not widely adopted
it could still replace FEBE
On Fri, Mar 30, 2012 at 9:11 AM, Andrew Dunstan and...@dunslane.net wrote:
On 03/30/2012 11:41 AM, Robert Haas wrote:
On Fri, Mar 30, 2012 at 10:55 AM, Dobes Vandermeerdob...@gmail.com
wrote:
Well, in our case HTTP is a clear win (but not replacement) and SPDY a
potential one (even as a
On Fri, Mar 30, 2012 at 10:21 AM, Daniel Farina dan...@heroku.com wrote:
Any enhancement here that can't be used with libpq via, say, drop-in
.so seems unworkable to me, and that's why any solution that is
basically proxying to the database is basically a non-starter outside
the very earliest
Hi guys,
Something from Josh's recent blog post about summer of code clicked with me
- the HTTP / SQL concept.
It was something I'd been thinking about earlier, how people really like
HTTP APIs and this is one of the drivers behind adoption of some NoSQL
databases out there.
Some things that I
On 03/29/2012 10:37 AM, Dobes Vandermeer wrote:
Hi guys,
Something from Josh's recent blog post about summer of code clicked
with me - the HTTP / SQL concept.
It was something I'd been thinking about earlier, how people really
like HTTP APIs and this is one of the drivers behind adoption
On Thu, Mar 29, 2012 at 8:04 AM, Andrew Dunstan and...@dunslane.net wrote:
1. I've been in discussion with some people about adding simple JSON extract
functions. We already have some (i.e. xpath()) for XML.
2. You might find htsql http://htsql.org/ interesting.
My colleagues and myself have
On Thu, Mar 29, 2012 at 12:57 PM, Daniel Farina dan...@heroku.com wrote:
D'oh, I munged the order.
More technical concerns:
* Protocol compression -- but a bit of sand in the gears is *which*
compression -- for database workloads, the performance of zlib can be
a meaningful bottleneck.
*
On Thu, Mar 29, 2012 at 11:04 PM, Andrew Dunstan and...@dunslane.netwrote:
On 03/29/2012 10:37 AM, Dobes Vandermeer wrote:
Hi guys,
Something from Josh's recent blog post about summer of code clicked with
me - the HTTP / SQL concept.
1. I've been in discussion with some people about
On Thu, Mar 29, 2012 at 6:25 PM, Dobes Vandermeer dob...@gmail.com wrote:
2. You might find htsql http://htsql.org/ interesting.
As a reference, or should we just bundle / integrate that with PostgreSQL
somehow?
It's a totally different language layer without wide-spread popularity
and, as
On Fri, Mar 30, 2012 at 3:59 AM, Daniel Farina dan...@heroku.com wrote:
On Thu, Mar 29, 2012 at 12:57 PM, Daniel Farina dan...@heroku.com
wrote:
More technical concerns:
* Protocol compression -- but a bit of sand in the gears is *which*
compression -- for database workloads, the
On Fri, Mar 30, 2012 at 3:57 AM, Daniel Farina dan...@heroku.com wrote:
On Thu, Mar 29, 2012 at 8:04 AM, Andrew Dunstan and...@dunslane.net
wrote:
Lastly, a case that can not as easily be fixed without some more
thinking is leveraging caching semantics of HTTP. think people would
On Thu, Mar 29, 2012 at 6:37 PM, Dobes Vandermeer dob...@gmail.com wrote:
On Fri, Mar 30, 2012 at 3:59 AM, Daniel Farina dan...@heroku.com wrote:
On Thu, Mar 29, 2012 at 12:57 PM, Daniel Farina dan...@heroku.com
wrote:
More technical concerns:
* Protocol compression -- but a bit of sand in
On Fri, Mar 30, 2012 at 10:55 AM, Daniel Farina dan...@heroku.com wrote:
On Thu, Mar 29, 2012 at 6:37 PM, Dobes Vandermeer dob...@gmail.com
wrote:
On Fri, Mar 30, 2012 at 3:59 AM, Daniel Farina dan...@heroku.com
wrote:
On Thu, Mar 29, 2012 at 12:57 PM, Daniel Farina dan...@heroku.com
24 matches
Mail list logo
