<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18975"></HEAD>
<BODY>
<DIV><SPAN class=605421120-17112010><FONT color=#000080 size=2
face="Lucida Sans">Please don't do that. We are always getting test failures
caused by someone having updated logs for databases X and Y but not
Z.</FONT></SPAN></DIV>
<DIV><SPAN class=605421120-17112010><FONT color=#000080 size=2
face="Lucida Sans"></FONT></SPAN> </DIV>
<DIV><SPAN class=605421120-17112010><FONT color=#000080 size=2
face="Lucida Sans">Even if log files weren't an issue, I believe that we should
define data types in the mondrian schema, not inherit them from the database
schema. People might want a measure stored in a NUMBER(38, 0) column in Oracle
to be represented as a java int. We should let them.</FONT></SPAN></DIV>
<DIV><SPAN class=605421120-17112010><FONT color=#000080 size=2
face="Lucida Sans"></FONT></SPAN> </DIV>
<DIV><SPAN class=605421120-17112010><FONT color=#000080 size=2
face="Lucida Sans">In physical schemas, to be introduced in mondrian-4, you will
be able to define the data types of the columns.</FONT></SPAN></DIV>
<DIV><SPAN class=605421120-17112010><FONT color=#000080 size=2
face="Lucida Sans"></FONT></SPAN> </DIV>
<DIV><SPAN class=605421120-17112010><FONT color=#000080 size=2
face="Lucida Sans">Julian</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #000080 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> Luc Boudreau
[mailto:lucboudreau@gmail.com] <BR><B>Sent:</B> Wednesday, November 17, 2010
11:59 AM<BR><B>To:</B> jhyde@pentaho.com<BR><B>Cc:</B> Mondrian developer
mailing list<BR><B>Subject:</B> Re: Eigenbase perforce change 13913 for
review<BR></FONT><BR></DIV>
<DIV></DIV>Yeah, I saw that after I checked it in. What I'll do is the same
approach as the SQL pattern detection tests. I want to extend the XML ref logs
and add an attribute to tell which response XML corresponds to which test
context database dialect. This way we won't have to bend the code in order to
support the test cases. You said that the original design was to avoid having
multiple ref logs, what about having something like:<BR><BR><SPAN
style="FONT-FAMILY: courier new,monospace"><test><BR>
(...)<BR> <response dialect="default"></SPAN><BR
style="FONT-FAMILY: courier new,monospace"><SPAN
style="FONT-FAMILY: courier new,monospace">
(...)</SPAN><BR style="FONT-FAMILY: courier new,monospace"><SPAN
style="FONT-FAMILY: courier new,monospace">
</response></SPAN><BR style="FONT-FAMILY: courier new,monospace"><SPAN
style="FONT-FAMILY: courier new,monospace"> <response
dialect="oracle"></SPAN><BR
style="FONT-FAMILY: courier new,monospace"><SPAN
style="FONT-FAMILY: courier new,monospace">
(...)</SPAN><BR style="FONT-FAMILY: courier new,monospace"><SPAN
style="FONT-FAMILY: courier new,monospace">
</response></SPAN><BR><SPAN
style="FONT-FAMILY: courier new,monospace"></test></SPAN><BR
clear=all><BR><BR><BR>
<DIV class=gmail_quote>On Tue, Nov 16, 2010 at 5:20 PM, Julian Hyde <SPAN
dir=ltr><<A
href="mailto:jhyde@pentaho.com">jhyde@pentaho.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>> Luc Boudreau wrote:<BR>><BR>> <A
href="http://p4web.eigenbase.org/@md=d&c=6PU@/13913?ac=10"
target=_blank>http://p4web.eigenbase.org/@md=d&c=6PU@/13913?ac=10</A><BR>><BR>>
Change 13913 by lucboudreau@luc-mondrian-3.2 on 2010/11/16
06:48:42<BR>><BR>> MONDRIAN-613 Missing xsd:type
attribute in drill-down<BR>> rowset makes Excel 2007 crash. Also, when
returning a<BR>> drillthrough query result, use the actual DB specified
type<BR>> for the row set XSD infos rather than the schema
infos.<BR><BR>Luc,<BR><BR>The trouble with inferring the XML type from the
database type is that the<BR>database type is different for every database.
So, your change has broken<BR>the drillthrough tests in XmlaBasicTest on
oracle. The previous behavior was<BR>mostly a matter of expediency, to avoid
maintaining multiple ref logs, one<BR>for each database.<BR><BR>Any ideas
how to fix this?<BR><BR>As it happens I'm working on XMLA drillthrough
support right now, so the<BR>test exceptions had me mighty puzzled for a
while.<BR><FONT
color=#888888><BR>Julian<BR><BR></FONT></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>