similar to: Patching ferret problems...

Hi, i''m working on a project using Ferret for indexing it''s datas. I''m very happy with it but i need to code an extension to implement a .to_json method to TopDocs class, because ruby''s json implementation is really really slow... It''s my second (the first was the tutorial :/ ) ruby C extension, so i''m not really at ease with ruby C

Hi all, I''ve posted that few weeks ago but no one answered, but this feature is REALLY important for us. I have many objects with a url field, of course containing standards urls... I''m trying to match them but i actually got problems with that. Here''s a little code of what i would like to achieve: require ''rubygems'' require

Hi :) Here''s a little code reproducing something that i consider as a bug, if it''s not please explain :] http://pastie.caboo.se/18693 Thanks by advance, Cheers, J?r?mie ''ahFeel'' BORDIER -- Posted via http://www.ruby-forum.com/.

> Here''s the dump... http://pastie.caboo.se/18686 ahFeel <= here''s the dumb :/ Cheers :) J?r?mie ''ahFeel'' BORDIER -- Posted via http://www.ruby-forum.com/.

Hi all :-) I''m experiencing strange document loss with Ferret 0.11.4 / Ruby 1.8.4. The index handles around 3000 documents, and sometimes during a query_update operation, the delete is done but not the add. That''s very random and happens after a lot of queries (many K). I''ve tried to look into Ferret''s C code, everything looks like going well, the add *LOOKS

I''ve tried 0.11.4, and it has not yet crashed, even after I removed (most of) the workarounds. However, the same is also true of 0.11.3... I haven''t seen any of these crashes for several days, which is a very good thing. I can''t remember all the workarounds I did to sidestep the crashing; some of them I don''t want to reverse because they actually were also

Hi, Just downloaded the new ferret 0.11. I''m on OSX btw. I get this error everytime I run my unit tests: Loaded suite ferret_updater_unit_test Started E/usr/local/lib/ruby/1.8/erb.rb:504: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [i686-darwin8.7.1] Abort trap When I revert back to 10.14 I dont get this error. When I comment out the line: Ferret::Index::Index.new({:path =>

I''m still having some crashes on my server that don''t seem to happen on my development system. One difference between them is that the server is running in 64bit mode. Are there any issues running ferret on a 64bit system? I''ve seen some old traffic on the subject but all from about 9 months ago. There are some warnings printed out when I install ferret on the

Here''s the deal: static TopDocs *isea_search_w(Searcher *self, Weight *weight, int first_doc, // OFFSET int num_docs, // LIMIT Filter *filter, Sort *sort, filter_ft filter_func,

Hi, I am trying to convert a hash to JSON using ActiveSupports built in .to_json. I am doing similar to the example below but are there certain strings that could go in place of ''bar'' or ''rez'' that will break the to_json method? I am using a very long string from rjs output in place of ''bar''. Perhaps .to_json is not ready yet? Thanks, Peter

I''m using [acts_as_commentable_with_threading](http://github.com/elight/acts_as_commentable_with_threading/), and it worked fine until I tried to overwrite the to_json function to include more details about the associated user. Here''s part of the comment class (which was originally defined in the plugin, but I moved it to the models folder, a move which seems not to affect the

I am trying to test drive ferret on a ubuntu dapper installation. I have a ferret-test.rb file like: ----begin--------- require ''ferret'' include Ferret index = Index::Index.new(:path => ''/opt/search-index'') ----end----------- When i issue: ruby ferret-test.rb, I get: ferret-test.rb:1:in `require'': no such file to load -- ferret (LoadError)

Hello, ActiveSupport::JSON::Variable.to_json is the only to_json without an "options" parameter. Is this intended? For example, this code in a .rjs page[@user.dom_id].visual_effect :drop_out, :afterFinish => ActiveSupport::JSON::Variable.new("foo") fails with ActionView::TemplateError: wrong number of arguments (1 for 0) On line #7 of

The way Rails handles root nodes in JSON and XML serialization is inconsistent. This has been discussed before: https://rails.lighthouseapp.com/projects/8994/tickets/2584-232-activeresource-json-doesnt-send-parameters-with-root-node This seems mostly taken care of with ActiveModel::Base.include_root_in_json, especially if/when it ends up in ActiveResource. However, there is also the issue of how

I''d really like to see just 2 more functional changes to the JSON serialization/encoding before we get to Rails 2.0. First, and I think this is really crucial because without it all the efforts to output JSON from ActiveRecord objects would have been half in vain, is to allow us to do this in controllers: @authors = Author.find(:all) render :json => @authors.to_json(:only =>

I need to reset the ferret index between test runs. It seems like there are a few ways to reset the ferret index. * Deleting the index directory -- is this really bad form? * calling rebuild_index * (any others?) What would y''all recommend? (Sorry, I''m from Texas) Preferably, I''d like a way to reset the index that I can integrate into a selenium test. -David

Hey there I was scratching my head over why my application breaks when I run on a local server but works on my remote server. It turns out that my local server is Rails 2.0.2 and my remote server is 1.2.3 and I expect the tag "attributes" to be passed with a json stream, before parsing. Unfortunately, this was dropped in 2.0.2. Is there any documentation on this? Any way to get it back?

Originally posted on github, reported to the right place. I would like to open a discussion about how `to_json` and `as_json` operates in Rails from a performance standpoint. I''m using Rails 3.2 but this issue applies to almost all versions of Rails. Our use case presents the challenge in sending out potentially large JSON (or XML, but we''ll focus on JSON rendering here)

I''m trying to write a helper method similar to attr_accessible but instead it will be used to whitelist which attributes are available for serialization (attr_serializable). My first attempt at this was to override serialized_hash and modify the :only option to include nothing but serializable attributes. I''m facing a problem when nested models are ''included''

Hi all, I''m working on a Backbone.js single page app with Rails 3.1, and in an attempt to save on HTTP requests, I want to embed initial data set in a HTML document that is sent back to the browser after successful login. I was thinking I can simply convert my ruby object to JSON, then HTML escape resulting string of JSON, and then use that as a value for JavaScript variable. Something