Forum: RSpec Who is using NullDB?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Avdi G. (Guest)
on 2009-01-13 01:39
(Received via mailing list)
I gather from some recent posts that some people are actually using
NullDB in their projects.  As the creator of NullDB, I'm pleased and a
little surprised to hear this.

Since NullDB is  has received exactly zero attention from me since
it's initial release, I'm curious how it's working out for people.

Do you use NullDB?

If so, do you use my baseline version
(http://svn.avdi.org/nulldb/trunk), or are you using a fork?

If a fork, which fork, and why?

Are there any bugs or feature requests you'd like to see addressed?

Thanks,

--
Avdi

Home: http://avdi.org
Developer Blog: http://avdi.org/devblog/
Twitter: http://twitter.com/avdi
Journal: http://avdi.livejournal.com
Ben M. (Guest)
on 2009-01-13 02:36
(Received via mailing list)
On 1/12/09 4:20 PM, Avdi G. wrote:
> (http://svn.avdi.org/nulldb/trunk), or are you using a fork?
>
> If a fork, which fork, and why?
>
> Are there any bugs or feature requests you'd like to see addressed?
>
> Thanks,
>
>

Hey Avdi,
I love nullDB, so thank you very much for making it!  After looking into
the various libs that disconnect AR from the DB I decided on nullDB due
to it's design decisions.

I have been using your SVN version I believe.  Although, I may of
grabbed it off of github a couple of times since that is easier for me.
So my first request would be for you to add it to github so your fork
can be the official one. :)  GitHub has an import from SVN feature which
is really nice and makes it painless to convert a SVN repo.  If you do
that I would be much more likely to fork it and submit patches.

There is one bug I have found that is quite annoying but I haven't
looked into fixing it yet.  If I remember correctly the bug is something
like this:

class Band < AR::Base
   has_many :members
end

#with nulldb:
band = Band.create!(:name => "Foo")
bar = Member.create!(:name => "Mr. Bar")
band.members << bar
band.members # => []

I understand the limitations of nullDB so I don't expect the above call
to update the member's band_id.  I do however, expect the newly added
member to appear in the AR association.   What I have found is that for
some reason the above will not work when that is the first time the
association is being used, but it will otherwise.  For example, this
workaround works:

band = Band.create!(:name => "Foo")
bar = Member.create!(:name => "Mr. Bar")
band.members.inspect # workaround for odd nullDB bug
band.members << bar
band.members # => [bar]

Does that make sense?

Other than that bug, and the problem with the adapter changing slowing
things down nullDB has been great. We are getting a lot of benefit from
it on our current project.
So once again, thanks!

-Ben
Pat M. (Guest)
on 2009-01-13 03:12
(Received via mailing list)
On Mon, Jan 12, 2009 at 3:20 PM, Avdi G. <removed_email_address@domain.invalid> 
wrote:
> (http://svn.avdi.org/nulldb/trunk), or are you using a fork?
>
> If a fork, which fork, and why?
>
> Are there any bugs or feature requests you'd like to see addressed?

Out of curiosity, how much faster is nulldb than using sqlite in-memory?

Pat
This topic is locked and can not be replied to.