When using 'CAST() as' clause in a query, .NET Framework is
unable to accurate gauge the precision of the DateTIme data
type. Instead,
it uses the maximum precision for the data type (Year to
fraction(5)). This becomes a problem when the cast is part of
SELECT ... UNION...
statement, and the precision of the cast does not match the
precision of a column type. In that scenario, the following
error results:
<m:internalexception><m:message>ERROR [IX000] [IBM][IDS/UNIX64]
Corresponding column types must be compatible for each UNION
statement. <----------------
</m:message><m:type>IBM.Data.DB2. DB2Exception</m:type><m:stack
trace> at IBM.Data.DB2.DB2Command.ExecuteReaderObject(Command
Behavior
behavior, String method, DB2CursorType reqCursorType, Boolean
abortOnOptValueChg, Boolean skipDeleted, Boolean isResultSet,
Int32
maxRows, Boolean skipInitialValidation) at
IBM.Data.DB2.DB2Command.ExecuteReaderObject(Comman dBehavior
behavior,
String method) at
IBM.Data.DB2.DB2Command.ExecuteReader(CommandBehavi or
behavior) at IBM.Data.DB2.DB2Command.ExecuteDbDataReader(Command
Behavior
behavior) at
System.Data.EntityClient.EntityCommandDefinition.E
xecuteStoreCommands(En
tityCommand entityCommand, CommandBehavior
behavior)</m:stacktrace></m:internalexception>
Operating system and level
Windows
Client, server, and gateway information
Client connects to server, no gateway involved.
Server information, if applicable
Will get an update defect.
How to reproduce the problem
Yunming Wang reports reproducing the problem with the test case
from defect wsdbu00956011. |
