dterrors@[EMAIL PROTECTED]
wrote:
> On Feb 4, 5:17 pm, "Paul Lautman" <paul.laut...@[EMAIL PROTECTED]
> wrote:
>> dterr...@[EMAIL PROTECTED]
wrote:
>> > On Feb 4, 4:55 pm, "Paul Lautman" <paul.laut...@[EMAIL PROTECTED]
>
>> > wrote:
>> >> dterr...@[EMAIL PROTECTED]
wrote:
>> >> > I can't do insert...select because the keys will all be
>> >> > different on the newly copied tables.
>>
>> >> Why?
>>
>> > Because I'm copying records. So therefore their keys will be
>> > different. Unique keys? Two records can't have the same key?
>>
>> But you are copying to new tables, so there will still only be one
>> of each key in the table.
>
> I'm copying to the same table.
>
> Although even if it was to a new table- how do I link up the binding
> table (table c)? Table c's value for db_a_id is no longer relevant.
> It may have "15" where there is no 15 in the new table (or 15 is
> something else).
>
> I'm trying to copy individual (set of records). As in "copy record 12
> of table a and include (also make copies of) everything that relates
> to it in table b, including the relation****p record in table c"
>
> The new relation****p record needs to be aware of the new a and b keys.
I quote: "I can't do insert...select because the keys will all be
different
on the newly copied tables."
If you were doing what you said you were doing, copying to new tables,
then
there would be no reason for the keys to change, in any of the 3 tables.
That is the reason I asked "why", because your question did not make
sense.
|
