My apologies for my late reply, I've been out for a while.
> -Original Message-
> From: Nikunj R. Mehta [mailto:nikunj.me...@oracle.com]
> Sent: Friday, December 11, 2009 10:47 AM
> To: public-webapps@w3.org WG
> Cc: Pablo Castro
> Subject: Re: [WebSimpleDB] All
I have gone ahead and updated the spec to allow option B (only).
Please take a look.
Nikunj
On Dec 8, 2009, at 10:14 AM, Nikunj R. Mehta wrote:
Hi Pablo,
Sorry for the long delay in responding to your comments. Hopefully,
we can continue the discussion now.
Schema changes interact with t
Hi Pablo,
Sorry for the long delay in responding to your comments. Hopefully, we
can continue the discussion now.
Schema changes interact with the locking model of the database. As I
see it, here are several ways in which the API could be designed and
the consequences of doing so:
A. Al
On 11/22/09 3:14 PM, Pablo Castro wrote:
Does this seem reasonable?
This seems reasonable to me. The use case makes sense, and is something
I've seen many times in real life.
Cheers,
Shawn
We are finding a number of reasons for wanting to create tables on the fly, and
without bumping up the database version. A few examples:
- Packaged components that create side tables to maintain its own state
- Query processors often need to "spill to disk" during query execution. For
example, so
