Issues - wycats/moneta

wycats / moneta

304

Description:

a unified interface to key/value stores

Sort by: Priority | Votes | Last Updated

Loading…

2.

1 vote

github hosted gem seems dated and buggy
3 comments Created 6 months ago by bumi

Title

Body
The github hosted gem seems dated: The Moneta::Memcache#key? method in the installed gem looks like: def key?(key) !self["key"].nil? end which does not work ("key" vs. key). Is there a way to update the gem? thanks.
or cancel
The github hosted gem seems dated:

The Moneta::Memcache#key? method in the installed gem looks like:

def key?(key)
```
!self["key"].nil?
```
end

which does not work ("key" vs. key).
Is there a way to update the gem?

thanks.
Comments
mwilliams Wed Jun 03 06:43:05 -0700 2009 | link
+1 for this. Pulled down the latest and the S3 additions didn't get included in the gem I installed.

sudo gem install wycats-moneta --no-rdoc --no-ri Successfully installed wycats-moneta-0.6.0

Shouldn't this line in the gemspec include everything in /lib/moneta?

s.files = ["LICENSE", "README", "Rakefile", "TODO", "lib/moneta", "lib/moneta/datamapper.rb", "lib/moneta/file.rb", "lib/moneta/memcache.rb", "lib/moneta/memory.rb", "lib/moneta/xa
Comment
+1 for this. Pulled down the latest and the S3 additions didn't get included in the gem I installed. sudo gem install wycats-moneta --no-rdoc --no-ri Successfully installed wycats-moneta-0.6.0 Shouldn't this line in the gemspec include everything in /lib/moneta? s.files = ["LICENSE", "README", "Rakefile", "TODO", "lib/moneta", "lib/moneta/datamapper.rb", "lib/moneta/file.rb", "lib/moneta/memcache.rb", "lib/moneta/memory.rb", "lib/moneta/xa
or cancel
wycats Tue Jul 14 22:43:00 -0700 2009 | link

I'll try and get to this before this weekend. It's tough keeping this up to date as I pull from multiple forks. Git isn't that good.

Comment
I'll try and get to this before this weekend. It's tough keeping this up to date as I pull from multiple forks. Git isn't *that* good.
or cancel

bumi Thu Jul 16 02:31:22 -0700 2009 | link

thanks.
Perhaps a note in the readme on how to build the gemspec and install the gem from a local cloned repo is enough?

Comment
thanks. Perhaps a note in the readme on how to build the gemspec and install the gem from a local cloned repo is enough?
or cancel

Parsed with GitHub Flavored Markdown
3.

0 votes

[Feature] Abstract value marshaling
0 comments Created 4 months ago by rykov

Title

Body
I noticed that some Moneta backends do backend.put(value) and some do backend.put(Marshal.dump(value)). I would like to be able to control which I use, because I have a legacy system that uses the former. But, I also see the value in having the latter. Furthermore, I can see how one would potentially want to write class-specific marshaling - for example, marshal just @attributes for ActiveRecord objects.
or cancel

I noticed that some Moneta backends do backend.put(value) and some do backend.put(Marshal.dump(value)). I would like to be able to control which I use, because I have a legacy system that uses the former. But, I also see the value in having the latter.

Furthermore, I can see how one would potentially want to write class-specific marshaling - for example, marshal just @attributes for ActiveRecord objects.

Comments

Parsed with GitHub Flavored Markdown

Labels

github hosted gem seems dated and buggy

Comments

[Feature] Abstract value marshaling

Comments