Hi, The permanent data is going to be stored separately but as data is parsed into fragments before indexing, it isn't a very good idea to rebuild the index...However, i was looking at rails just to provide the front-end to the indexing and searching that would go on in the backend, which doesn't really justify it's usage but i thought it would probably give more flexibility dealing with the index..I am hoping to make a model based on an index so it can communicate easily with the core program and work it out from there, but it'll need some reading as I only started rails today..
Thanks a lot, Pulkit On 8/14/07, Benjamin Krause <[EMAIL PROTECTED]> wrote: > > > > The only problem is, as this list demonstrates, Ferret indexes aren't > > always the most reliable place to store your data. I'd advise keeping a > > permanent copy in files or a database somewhere so you can rebuild the > > index if it gets corrupted or when the Ferret version changes. > > i agree to that.. it might not be a problem, if you have a static index > that never changes. but as soon as your index evolves, you will find > yourself in a situation where an index rebuild is necessary. > > Ben > > > _______________________________________________ > Ferret-talk mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ferret-talk > -- The dumb's song to the deaf is exactly what music is to us. The best things in the world are free. A foolish dreamer who knows reality is more vague than a dream and that a song's "realer" than the same makes reality. Pulkit Bhuwalka Dept. Of Information Science BMS College Of Engineering, Bangalore
_______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
