Re: partitionning join table and normalization

In fact, even if i use
SELECT ACP_ID,

       MAX(DECODE(ID_FIELD, 1, DATA)) AS ded,
       MAX(DECODE(ID_FIELD, 2, DATA)) AS qsqd,
       MAX(DECODE(ID_FIELD, 3, DATA)) AS dsv,
       MAX(DECODE(ID_FIELD, 4, DATA)) AS ntrg,
       MAX(DECODE(ID_FIELD, 5, DATA)) AS yj,
       MAX(DECODE(ID_FIELD, 6, DATA)) AS dsq,
       MAX(DECODE(ID_FIELD, 7, DATA)) AS df,
       MAX(DECODE(ID_FIELD, 8, DATA)) AS ee,
       MAX(DECODE(ID_FIELD, 9, DATA)) AS er,
       MAX(DECODE(ID_FIELD, 10, DATA)) AS gf,
       MAX(DECODE(ID_FIELD, 11, DATA)) AS rezg,
       MAX(DECODE(ID_FIELD, 12, DATA)) AS f,
       MAX(DECODE(ID_FIELD, 13, DATA)) AS fds,
       MAX(DECODE(ID_FIELD, 14, DATA)) AS fdsv,
       MAX(DECODE(ID_FIELD, 15, DATA)) AS vf,
       MAX(DECODE(ID_FIELD, 16, DATA)) AS zz,
       MAX(DECODE(ID_FIELD, 17, DATA)) AS k_INF,
       MAX(DECODE(ID_FIELD, 18, DATA)) AS bvr,
       MAX(DECODE(ID_FIELD, 19, DATA)) AS d

The problem appear when i want to use a view which not including the condition on id.
If this problem can be solves, what about my initial question : Is it possible to create a partitionnal table on fields coming from a join table ?

Chmanu Received on Wed Apr 09 2008 - 07:30:08 CDT