<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1528" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=113541709-30032006>The
indexes in rdbms are first-class tables, and all index updates are performed
within a transaction context. Thus, solving the partitioned network problem will
be done in roughly the same way (I assume you mean setting master
nodes?)</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=113541709-30032006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=113541709-30032006>There
is (more or less) also a rebuild_indexes(Tab) function, using a mnesia_recover.
It's mainly used for adding indexes to existing tables and populating them
within the scope of a schema transaction.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=113541709-30032006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=113541709-30032006>One
can also, of course, break the abstraction and simply clobber the rdbms indexes
and rebuild them by hand (by bypassing the wrapper functions in rdbms). I could
make this a bit simpler and clearly documented, if it's deemed
necessary.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=113541709-30032006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=113541709-30032006>BR,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=113541709-30032006>Ulf
W</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> chandru
[mailto:chandrashekhar.mullaparthi@gmail.com] <BR><B>Sent:</B> den 30 mars
2006 10:48<BR><B>To:</B> Ulf Wiger (AL/EAB)<BR><B>Cc:</B>
erlang-questions@erlang.org<BR><B>Subject:</B> Re: Mnesia and additional
indexes: a cautionary tale<BR></FONT><BR></DIV>
<DIV></DIV>On 30/03/06, <B class=gmail_sendername>Ulf Wiger (AL/EAB)</B>
<<A href="mailto:ulf.wiger@ericsson.com">ulf.wiger@ericsson.com</A>>
wrote:
<DIV><SPAN class=gmail_quote></SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><BR>Enter
the 'rdbms' contrib...<BR><BR>I see a couple of traits of the additional
indexing<BR>support in rdbms that could help in this<BR>particular
situation:<BR><BR>- You can have disc_copy indexes, which are not rebuilt
<BR> every time mnesia is restarted</BLOCKQUOTE>
<DIV><BR>Is the case where mnesia recovers from a partitioned network taken
care of? The index tables will have to be rebuilt in this case. I'm sure you
would've but I thought I'll ask anyway. <BR><BR>cheers<BR>Chandru<BR><BR>PS:
haven't used rdbms (yet)<BR></DIV></DIV><BR></BLOCKQUOTE></BODY></HTML>