[erlang-questions] Strange behaviour of ets
Wed Feb 27 13:55:17 CET 2008
The problem is that your shell process is the owner of ets table. When you
make incorrect operation it dies with its ets tables and new shell process
created without any. Just run self() before and after error.
You should create ets in external process via spawn or add catch to function
Maxim Treskin-2 wrote:
> I see some strange behaviour of ets interaction.
> After I did an error in ets:select request, all following requests are
> erroneous until, i.e. ets:new
> Why this error happens?
View this message in context: http://www.nabble.com/Strange-behaviour-of-ets-tp15711918p15712654.html
Sent from the Erlang Questions mailing list archive at Nabble.com.
More information about the erlang-questions