Le 28 août 08 à 09:25, Jens Krämer a écrit :
I must admit that I don’t do regular testing with postgresql, maybe
its some db related issue. I’ll look into it. Could you please open
a ticket at projects.jkraemer.net/acts_as_ferret ?
Thanks for your quick reply.
I think I found a mistake of mine with this other thread :
Le 28 août 08 à 17:19, Sheldon M. a écrit :
Now, corrupt indexes in development is another issue. In
development, you are not running a DRb server. Each mongrel is
hitting the index directly. You typically have only one mongrel
running in development. But if you open an interactive script/
console session, and play with your models side-by-side a running
mongrel, you WILL corrupt your Ferret index. That’s because both
the mongrel and the script/console will be writers to the same
index, something that Ferret doesn’t support. Heck, running a rake
db:migrate along side a running mongrel will cause index
corruption, for the same reason: multiple writers.
In fact I probably had mongrel and console running together when I
reindexed in development.
I shut down and dropped my index dir, then did bulk_index on my class
Seems all my words were indexed.
Maybe we could think to some error messages issued by each index
could be like
logger.debug ‘Man, chances are you are messing up your index by
writing concurrently to it’ if (development) && writer_flag
The flag being a development only feature, enabled by default,
disabled in production only.
What do you think of this ?