During the DD deploy, a DCR is converted to a table record. The table has a primary key as autogenerated sequence (oracle) or identity (sql). What will be the dbschema look like? If the dbschema does not contain the identity field, it might not be an issue for creation (considering identity is increment automatically) but it might be an issue for update. I have following tables for detail (see dd.552.admin.pdf pg 101, cut and paste the following text to a html editor).
<table width="75%" border="1">
<tr>
<td>Title</td>
<td>Author</td>
<td>ISBN</td>
<td>Price</td>
</tr>
<tr>
<td>Interwoven</td>
<td>Author1</td>
<td>12345</td>
<td>100.00</td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
</table>
<p>table 1</p>
<table width="75%" border="1">
<tr>
<td>Title</td>
<td>Reviewers</td>
</tr>
<tr>
<td>Interwoven</td>
<td>R1</td>
</tr>
<tr>
<td>Interwoven</td>
<td>R2</td>
</tr>
<tr>
<td>Interwoven</td>
<td>R3</td>
</tr>
<tr>
<td>Interwoven</td>
<td>R4</td>
</tr>
</table>
<p>table 2</p>
Table 1 and 2 use title as primary key and reference.
<table width="75%" border="1">
<tr>
<td>ID</td>
<td>Title</td>
<td>Author</td>
<td>ISBN</td>
<td>Price</td>
</tr>
<tr>
<td>1</td>
<td>Interwoven</td>
<td>Author1</td>
<td>12345</td>
<td>100.00</td>
</tr>
<tr>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
</tr>
</table>
<p>table 3</p>
<table width="75%" border="1">
<tr>
<td>ID</td>
<td>Reviewers</td>
</tr>
<tr>
<td>1</td>
<td>R1</td>
</tr>
<tr>
<td>1</td>
<td>R2</td>
</tr>
<tr>
<td>1</td>
<td>R3</td>
</tr>
<tr>
<td>1</td>
<td>R4</td>
</tr>
</table>
table 3 and 4 use ID as primary key and reference. What will be the sample dbschema section look like? Is this a good approach to have a hidden identity field rather than an explicit input field as primary key.
Thanks,
Albert
Edited by zhongal on 09/07/03 08:14 AM (server time).
