For the archives.... It was not a problem with contents of index files but a) some files were not copied properly and b) some slight behavioural change in ferret (?) required app to issue additional doc.load for some indexes before field values could be accessed...
Everything works just fine now... izidor On 17.12.2007, at 17:25, Izidor Jerebic wrote: > > Yes, but that was copy from Intel to Intel hardware. I copied from > Intel to PowerPC hardware. You know, endiannes and all that... > > izidor > > On 17.12.2007, at 17:17, Paul Lynch wrote: > >> I have copied Ferret index files from a Redhat Linux machine to a >> Windows Vista machine, and they worked. I haven't tried it on a Mac, >> though. >> >> On Dec 17, 2007 6:49 AM, Izidor Jerebic <[EMAIL PROTECTED]> >> wrote: >>> Hello! >>> >>> I am trying to read Ferret index files from Windows machine on my >>> Mac >>> G5 Leopard machine, but the following returns nil: >>> >>> Ferret::Index::IndexReader.new( index_paths ) >>> >>> Should this work? Are index files guaranteed to be platform >>> independent or not? Is there any problem if files (top direectory) >>> are renamed? >>> >>> >>> izidor >>> >>> P.S. I can create the index myself and then everything works. >>> >>> _______________________________________________ >>> Ferret-talk mailing list >>> [email protected] >>> http://rubyforge.org/mailman/listinfo/ferret-talk >>> >> >> >> >> -- >> Paul Lynch >> Aquilent, Inc. >> National Library of Medicine (Contractor) >> _______________________________________________ >> Ferret-talk mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/ferret-talk > _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
