I have some big tables with disc_only_copies type. Now I need change short node nam开发者_开发知识库e to long but cannot do it with RAM limitation...
I am trying to have a function that ensures the table I need is already created and if not to create it. Here\'s the sample:
I have a bad node (it doesn\'t exist) in the mnesia cluster data when I get: > mnesia:system_info(db_nodes)
I am running two erlang nodes with a replicated mnesia database. Whenever I tried to start one of them while mnes开发者_开发百科ia IS NOT Running on the other one, mnesia:wait_for_tables(?TABS,?TIMEOU
I\'ve run into a problem w开发者_如何学运维here I cannot stop mnesia within my program without causing the app to hang.
I\'m digging into ejabberd but I can\'t find a way to inspect its Mnesia tables. Is there something like the开发者_Go百科 MySQL shell to inspect tables?You may use the Table Visualizer, in module tv.
Is there a standard place to put the mnesia database within erlang? At the moment I 开发者_如何学JAVAam putting it in the priv directory.By default, Mnesia will create the schema in a subdirectory cal
Suppose i have an application A which depends on mnesia with disk-enabled schema being present. What i\'d like to do is ensure that mnesia is running and allowing disc_copiestables
What is the best practice to accessing a single running mnesia node from another Erlang shell to only view data in the tables?
am josh in Uganda. i created a mnesia fragmented table (64 fragments), and managed to populate it upto 9948723 records. Each fragment was a disc_copies type, with two replicas.
加载中,请稍侯......