Izit Izit wrote:> Correction on my previous post. > > The correct way to do it is: > > Product.find_by_contents("*",{},:conditions =>search_conditions,:include > => [:supplier],:order =>"products.id" ) > > Leave out the :limit=>:all that is put in by default.Exactly - I tried to make aaf a bit more clever by letting it assume :limit => :all whenever sql conditions are given, but messed it up somehow ;-) It''s fixed in trunk (http://projects.jkraemer.net/acts_as_ferret/changeset/286), or just apply the attached patch. Btw, this whole thread hasn''t come through to the mailing list (yet?), I discovered it by pure chance. Please subscribe to the ferret mailing list (http://rubyforge.org/mail/?group_id=1028) and post there directly to make sure your posting gets actually read. Cheers, Jens Attachments: http://www.ruby-forum.com/attachment/1044/fix_limit_all.diff -- Posted via http://www.ruby-forum.com/.
John Bachir
2007-Nov-28 02:11 UTC
[Ferret-talk] flakey web-list interface (was: search not working after upgrade)
On Nov 26, 2007, at 4:11 PM, Jens Kr?mer wrote:> Btw, this whole thread hasn''t come through to the mailing list > (yet?), I > discovered it by pure chance. Please subscribe to the ferret mailing > list (http://rubyforge.org/mail/?group_id=1028) and post there > directly > to make sure your posting gets actually read.Jens- I see this happy a lot on rubyforge-- is it because it only brings email in from the web interface when the poster is subscribed? Or is it just flakey software? Do you have any insight into how we might be able to get rubyforge to either address or document this issue? John
Jens Kraemer
2007-Nov-28 09:14 UTC
[Ferret-talk] flakey web-list interface (was: search not working after upgrade)
On Tue, Nov 27, 2007 at 09:11:35PM -0500, John Bachir wrote:> > On Nov 26, 2007, at 4:11 PM, Jens Kr?mer wrote: > > Btw, this whole thread hasn''t come through to the mailing list > > (yet?), I > > discovered it by pure chance. Please subscribe to the ferret mailing > > list (http://rubyforge.org/mail/?group_id=1028) and post there > > directly > > to make sure your posting gets actually read. > > Jens- > > I see this happy a lot on rubyforge-- is it because it only brings > email in from the web interface when the poster is subscribed? Or is > it just flakey software? Do you have any insight into how we might be > able to get rubyforge to either address or document this issue?I''m not sure why this happens, maybe some spam prevention kicks in, or it''s the way you said, that it only accepts messages from people subscribed to the mailing list. I''ll try and ask Andreas Schwarz, the creator of ruby-forum.com, about this. Cheers, Jens -- Jens Kr?mer webit! Gesellschaft f?r neue Medien mbH Schnorrstra?e 76 | 01069 Dresden Telefon +49 351 46766-0 | Telefax +49 351 46766-66 kraemer at webit.de | www.webit.de Amtsgericht Dresden | HRB 15422 GF Sven Haubold, Hagen Malessa
Hello, I have some major problems on installing ferret on Leopard. While I know its already installed when you install Leopard I want to do it manually as I am not using the installed version of ruby (since I migrated from Tiger). When the native extensions are compiled I get some linker problems. Can anyone reproduce that? I have an older version of ferret installed (which I installed while being on Tiger) and this works fine, but I want to upgrade. Regards Till
On 28.11.2007, at 10:25, Till Vollmer wrote:> I have some major problems on installing ferret on Leopard.Interestingly, the words "major problems" and "Leopard" coincide a lot lately. Here''s my advice: - get rid of the probably buggiest piece of software that apple has ever shipped - go back to tiger and stay there for at least a couple of major updates - oh and if you made the same mistake and updated tiger instead of a fresh install, I''m very sorry for you ;)> When the native extensions are compiled I get some linker problems.If you can''t resist the temptation of leopard''s amazingly great feature set - make sure you install the latest ruby version as well as any other package via macports - have apple''s developer tools installed in advance (includes gcc + build tools) - a talisman might probably be helpful Best of luck, Andy
On Nov 28, 2007, at 7:36 AM, Andreas Korth wrote:> > On 28.11.2007, at 10:25, Till Vollmer wrote: > >> I have some major problems on installing ferret on Leopard. > > Interestingly, the words "major problems" and "Leopard" coincide a lot > lately. > > Here''s my advice: > > - get rid of the probably buggiest piece of software that apple has > ever shipped> > If you can''t resist the temptation of leopard''s amazingly great > feature set > > - make sure you install the latest ruby version as well as any other > package via macports > - have apple''s developer tools installed in advance (includes gcc + > build tools) > - a talisman might probably be helpfulFor what it''s worth, I''ve had zero problems with the Apple-supplied ruby, rails, etc... I updated some gems but ferret is running great (better than on our Linux servers, in fact -- no end of problems on Ubuntu 7.04 x64). I would recommend sticking with the Apple-supplied ruby; for once they''ve gotten it right, and everything seems to work beautifully.
On 28.11.2007, at 19:36, Noah M. Daniels wrote:>> Interestingly, the words "major problems" and "Leopard" coincide a >> lot >> lately.> For what it''s worth, I''ve had zero problems with the Apple-supplied > ruby, rails, etc...Frankly, knowing that everything works well for others isn''t worth much to people who _are_ having problems ;) But it appears to be a common reaction ? especially in the Apple community.> I would recommend sticking with the Apple-supplied > ruby; for once they''ve gotten it right, and everything seems to work > beautifully.You must have a different understanding of ''getting it right''. Here''s what I got when I entered ''ruby -v'' or ''gems'' into the console of a fresh 10.5 install: -bash: ruby: command not found After getting it to work eventually, a ''gem update --system'' just wrecked the whole Ruby installation. At that point I just gave up and installed Ruby/Gems and Rails via Macports. One thing I''d really like to know is how one is supposed to update the Ruby/Rails packages which shipped with Leopard. I had no chance to check, but are they still shipping Rails 1.1.2? I bet that Apple isn''t going to update Ruby during the whole lifetime of Leopard. Anything else would be a big surprise. So here goes my advice again: Use Macports. Do not use whatever Apple ships. Cheers, Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/ferret-talk/attachments/20071129/c1e5c6a6/attachment.html
On Nov 29, 2007, at 7:01 AM, Andreas Korth wrote:> > On 28.11.2007, at 19:36, Noah M. Daniels wrote: > >>> Interestingly, the words "major problems" and "Leopard" coincide a >>> lot >>> lately. > >> For what it''s worth, I''ve had zero problems with the Apple-supplied >> ruby, rails, etc... > > Frankly, knowing that everything works well for others isn''t worth > much to people who _are_ having problems ;) > > But it appears to be a common reaction ? especially in the Apple > community.Point taken, but I was responding to the poster''s statement that they''d avoided the apple-supplied Ruby.> > > You must have a different understanding of ''getting it right''. > Here''s what I got when I entered ''ruby -v'' or ''gems'' into the > console of a fresh 10.5 install: > > -bash: ruby: command not found >That''s very strange, but just sounds like a path issue.> After getting it to work eventually, a ''gem update --system'' just > wrecked the whole Ruby installation. At that point I just gave up > and installed Ruby/Gems and Rails via Macports. >Yes, this one is a known issue. See these links: http://discussions.apple.com/thread.jspa?threadID=1200950&tstart=0 http://discussions.apple.com/thread.jspa?threadID=1202925&tstart=0> One thing I''d really like to know is how one is supposed to update > the Ruby/Rails packages which shipped with Leopard. I had no chance > to check, but are they still shipping Rails 1.1.2? I bet that Apple > isn''t going to update Ruby during the whole lifetime of Leopard. > Anything else would be a big surprise. >It comes with rails 1.2.3, and gem update rails updates it to 1.2.5 (well, now 1.2.6) just fine.> So here goes my advice again: Use Macports. Do not use whatever > Apple ships.I disagree in the most friendly way possible :)
On Nov 29, 2007, at 4:01 AM, Andreas Korth wrote:> Here''s what I got when I entered ''ruby -v'' or ''gems'' into the > console of a fresh 10.5 install: > > -bash: ruby: command not foundCurious. Did you install the developer tools? Here''s what I get in Terminal with a fresh install of 10.5 and XCode 3.0: /Users/marvin/ $ ruby -v ruby 1.8.6 (2007-06-07 patchlevel 36) [universal-darwin9.0] /Users/marvin/ $ which ruby /usr/bin/ruby Marvin Humphrey Rectangular Research http://www.rectangular.com/