Sean Chittenden <[EMAIL PROTECTED]> said:
> Having thought about this for a min or three, I think the best solution
> would be the following:
>
> BEGIN;
> CREATE TEMP TABLE newmsg (
> .... -- Whatever schema is necessary
> ) ON COMMIT DROP;
> INSERT INTO other_tbl SELECT foo1, foo2, ${user_id} FROM newmsg;
> -- repeat insert as necessary
> COMMIT;
The only problem I can think of is foreign-key relationships that require
one or more physmessages to point to a messageblk. We'll also need a
special version of db_copymsg that selects from the temp table rather than
the disk table.
This can probably be done within the 2.0 series as it is 100% under the
hood.
Aaron
