<br><font size=2 face="sans-serif">We can go for the option #1. I mentioned
the new bug as low priority since probably it is a rare scenario where
calculated literal members get used in a mdx.</font>
<br>
<br><font size=2 face="sans-serif">-Ajit</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Julian Hyde"
<jhyde@pentaho.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: mondrian-bounces@pentaho.org</font>
<p><font size=1 face="sans-serif">04/11/2008 12:40 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
jhyde@pentaho.com; Please respond to<br>
Mondrian developer mailing list <mondrian@pentaho.org></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"'Mondrian developer mailing list'"
<mondrian@pentaho.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: [Mondrian] Native vs. Regular Non
Empty <Level>.MEMBERS Issue</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 color=#000080 face="Verdana">General principles:</font>
<br><font size=3> </font>
<br><font size=2 color=#000080 face="Verdana">1. Default behavior should
be the same as SSAS.</font>
<br><font size=2 color=#000080 face="Verdana">2. Behavior should be the
same for native and in-memory non empty.</font>
<br><font size=3> </font>
<br><font size=2 color=#000080 face="Verdana">If you don't like the default
behavior, you can add a property, disabled by default of course.</font>
<br><font size=3> </font>
<br><font size=2 color=#000080 face="Verdana">I would view differences
between 'native non empty' and 'in-memory non empty' behavior as serious
bugs. It's extremely confusing for an end-user to get different results,
and it makes it more difficult to support the product, since people don't
generally post their settings when they have a bug.</font>
<br><font size=3> </font>
<br><font size=2 color=#000080 face="Verdana">Based on these principles,
what action should we take? Sounds like option #1, except that the bug
would be high priority. Correct me if I'm wrong.</font>
<br><font size=3> </font>
<br><font size=2 color=#000080 face="Verdana">Julian</font>
<br>
<br>
<br>