search for: id_array

Sort of a newbie question - sorry if it''s been asked before and I missed it in my search. I have an id_array of Author ids, and I want to retrieve the associated Author models as quickly as possible, but also preserve the ordering of the id_array. Using Author.find(id_array) returns the records, but not in the same order. Is there some flag I can pass to find() to preserve the order? I want to avoid loo...

when i used "find_by_contents" on a legacy table with a different primary_key than "id" i always got results=nil even when total_hits was > 0 as a quick fix i changed line 261 in "class_methods.rb" from: conditions = [ "#{self.table_name}.id in (?)", id_array ] to: conditions = [ "#{self.table_name}.#{self.primary_key} in (?)", id_array ] i tried to report that as a ticket on projects.jkraemer.net/acts_as_ferret/ but something is broken there :( -> internal error "Akismet rejected spam" -- Posted via http://www.ruby-forum.c...

Hi, I''m running the trunk version with drb server. In my ferret_server.log I get a lot of messages like this: #method_missing(:add, ["User", {:first_name=>"blah", :comments=>nil, :company=>"blah", :phone_day=>""}]) Over and over again. But more importantly, since yesterday doing a search has caused an exception: A NoMethodError

I''m having an odd problem with Ferret 0.9.5 and acts_as_ferret 0.2.3, on RedHat Linux Enterprise 4. All of my find_by_contents calls return 0 results. When I try Foo.rebuild_index via the console, it returns nil. This is happening on my production machine, during deployment of my app. Everything works perfectly on my development machine (Windows). I have no idea where to start

hello, I am actually indexing thousands of 1ko text documents using ferret and acts_as_ferret, and i face performance problems. I takes me hours to index 20 000 1ko text documents. Methology used : I create and object, fulfill it with the text, and save it. So it is automaticly indexed. Is there a way to make it faster ? ( remove the auto optimize option somewhere ?) Thank you if you have any

find_by_contents will fail if you specify :include in the find_options parameter. The problem is on line 313: 313: conditions = [ "id in (?)", id_array ] 314: # combine our conditions with those given by user, if any 315: if find_options[:conditions] 316: cust_opts = find_options[:conditions].dup 317: conditions.first << " and " << cust_opts.shift 318: conditions.concat(cust_opts) 319: end 320: result = self.find(:all,...

How would you go about searching only a specific set of IDs in acts_as_ferret? Should I just create a huge "or" query or is there a more stylish way? Thanks, Winton -- Posted via http://www.ruby-forum.com/.

Further cleanup of the hv drivers. 1) Cleanup reference counting. 2) Handle all block devices using the storvsc driver. I have modified the implementation here based on Christoph's feedback on my earlier implementation. 3) Fix bugs. 4) Accomodate some host side scsi emulation bugs. 5) In case of scsi errors off-line the device. This patch-set further reduces the size of

Further cleanup of the hv drivers. 1) Cleanup reference counting. 2) Handle all block devices using the storvsc driver. I have modified the implementation here based on Christoph's feedback on my earlier implementation. 3) Fix bugs. 4) Accomodate some host side scsi emulation bugs. 5) In case of scsi errors off-line the device. This patch-set further reduces the size of

Further cleanup of the hv drivers. 1) Implement code for autoloading the vmbus drivers without using PCI or DMI signatures. I have implemented this based on Greg's feedback on my earlier implementation. 2) Cleanup error handling across the board and use standard Linux error codes. 3) General cleanup Regards, K. Y

Further cleanup of the hv drivers. 1) Implement code for autoloading the vmbus drivers without using PCI or DMI signatures. I have implemented this based on Greg's feedback on my earlier implementation. 2) Cleanup error handling across the board and use standard Linux error codes. 3) General cleanup Regards, K. Y

Further cleanup of the hv drivers. Back in June I had sent two patch sets to address these issues. I have addressed the comments I got from the community on my earlier patches here: 1) Implement code for autoloading the vmbus drivers without using PCI or DMI signatures. I have implemented this based on Greg's feedback on my earlier implementation. 2) Cleanup error handling across

Further cleanup of the hv drivers. Back in June I had sent two patch sets to address these issues. I have addressed the comments I got from the community on my earlier patches here: 1) Implement code for autoloading the vmbus drivers without using PCI or DMI signatures. I have implemented this based on Greg's feedback on my earlier implementation. 2) Cleanup error handling across