John R Pierce wrote:
chris wood wrote:
At a detailed level (which is NOT the direction I want this thread to
go) I do not agree with your statement that my proposal has no “hope
of ACID compliance or transactional integrity”. When the “slices” are
stored back to the cloud, this is the equivale
chris wood wrote:
At a detailed level (which is NOT the direction I want this thread to
go) I do not agree with your statement that my proposal has no “hope
of ACID compliance or transactional integrity”. When the “slices” are
stored back to the cloud, this is the equivalent of a commit and the
> yet you propose dumbing down the database even farther, without any hope
of ACID
> compliance, without any transactional integrity, indeed, without even
really being
> relational ?
> at least, thats what I get from my first read of it.
OK so you are a theorist/perfectionist, I can respect
chris wood wrote:
Apology in advance, this is not a bug, just wanted to ask if the
following issue is being considered:
Cloud computing seems to be quickly gaining ground as a deployment
technology for web apps.
From what I see this has not been good for Postgres. Google App Engine
cannot
Apology in advance, this is not a bug, just wanted to ask if the following
issue is being considered:
Cloud computing seems to be quickly gaining ground as a deployment
technology for web apps.
>From what I see this has not been good for Postgres. Google App Engine
cannot use Postgres and
A
