This thread brings me to some thoughts.
We could maybe achieve something like what you desire the following way:
1) Make sure "version" information is placed into .couch files in some way
if it isn't yet, from 1.0 forward.
2) Allow couch to read and convert files produced by an older version.
3)
Intermittent HTTP 500 errors on queries, no useful diagnostics
--
Key: COUCHDB-394
URL: https://issues.apache.org/jira/browse/COUCHDB-394
Project: CouchDB
Issue Type: Bug
On Thu, Jun 25, 2009 at 1:01 AM, Michael McDaniel wrote:
>
> On Thu, Jun 25, 2009 at 12:11:51AM -0400, Paul Davis wrote:
>> I've gotten tired of looking at compiler warnings when compiling
>> CouchDB but I figure I'd better ping the list before going through and
>> just updating everything.
>>
>> F
On Thu, Jun 25, 2009 at 12:11:51AM -0400, Paul Davis wrote:
> I've gotten tired of looking at compiler warnings when compiling
> CouchDB but I figure I'd better ping the list before going through and
> just updating everything.
>
> For reference almost all the errors are about the deprecated rege
> What makes it interesting from my perspective is that the data isn't in
> scary SQL tables, but in a more normal format that my Dad, or even, dare I
> say it, my manager can understand.
Golden.
"]" is Wojciech Kaczmarek
on Wed, 24 Jun 2009 18:03:12 +0200
] On Wed, Jun 24, 2009 at 04:17, Dale Wiles ">" wrote:
] Replication and distribution is where CouchDB really shines and it's not
] scary at all :). It's good especially for business because you can save
] lots of money this way,
I've gotten tired of looking at compiler warnings when compiling
CouchDB but I figure I'd better ping the list before going through and
just updating everything.
For reference almost all the errors are about the deprecated regexp
module and deprecated guards.
The guards look to pretty much be gua
Ohai,
whilst playing around with some url encoding edge cases (for http://www.phpcouch.org/)
, I came across the following two issues:
a) for a document "foo" with attachment "bar/baz", both "foo/bar/baz"
and "foo/bar%2Fbaz" work. I believe that only the latter should be
possible as that w
I forgot to mention that I'm not a CouchDB dev and I don't speak for the
creators, just take it as a voice of a dedicated user :]
On Wed, Jun 24, 2009 at 18:03, Wojciech Kaczmarek wrote:
> Hi! Just 3 cents..
>
> On Wed, Jun 24, 2009 at 04:17, Dale Wiles wrote:
>
>> I've been following CouchDB for
Hi! Just 3 cents..
On Wed, Jun 24, 2009 at 04:17, Dale Wiles wrote:
> I've been following CouchDB for a while and I'm really impressed with the
> way it's coming along.
>
> However, like >90% of the users out there, I'm not a business and I don't
> really care about replication and daemons and sc
Hello David,
I'm not well informed of the rationale behind slash encoding, but I did
check your experience against the wiki.
a) for a document "foo" with attachment "bar/baz", both "foo/bar/baz" and
> "foo/bar%2Fbaz" work. I believe that only the latter should be possible as
> that would be consi
On Jun 24, 2009, at 7:55 AM, Elliot Murphy wrote:
On 06/23/2009 10:17 PM, Dale Wiles wrote:
I've been following CouchDB for a while and I'm really impressed
with the way it's coming along.
However, like>90% of the users out there, I'm not a business and I
don't really care about replicati
Ohai,
whilst playing around with some url encoding edge cases (for http://www.phpcouch.org/)
, I came across the following two issues:
a) for a document "foo" with attachment "bar/baz", both "foo/bar/baz"
and "foo/bar%2Fbaz" work. I believe that only the latter should be
possible as that w
On 06/23/2009 10:17 PM, Dale Wiles wrote:
I've been following CouchDB for a while and I'm really impressed with the way
it's coming along.
However, like>90% of the users out there, I'm not a business and I don't really
care about replication and daemons and scary things that go bump in the ker
On Tue, Jun 23, 2009 at 05:46:52PM +0100, Noah Slater wrote:
> On Tue, Jun 23, 2009 at 09:26:23AM +0100, Brian Candler wrote:
> > As an aside: I support that subtly different encodings of the "same"
> > document (according to NFC) should have different revs, because (a) it's
> > unlikely that multi
15 matches
Mail list logo
