Re: Partitioning option for COPY

Hannu Krosing wrote:<br /><blockquote cite="mid:1259189910.30357.200.camel@hvost1700" type="cite"><pre wrap="">After
triggerscan't change tuple, thus cant change routing. </pre></blockquote> An after trigger can always issue an update
ofthe tuple but that should be trapped by the regular mechanism that will deal with updates (when we have it
available).<br/><blockquote cite="mid:1259189910.30357.200.camel@hvost1700" type="cite"><blockquote type="cite"><pre
wrap="">Alsothe description omits the execution of before and after statement 
 
triggers. While those can apply to the parent table (but the same 
question about what happens if the after statement modifies routing 
decision still applies), what does it mean in the case of COPY to have 
statement triggers on the child tables?    </pre></blockquote><pre wrap="">
What statement triggers do you mean ?

I don't think we have ON COPY triggers ?  </pre></blockquote> I mean <br /><pre class="SYNOPSIS">CREATE TRIGGER <tt
class="REPLACEABLE"><i>name</i></tt>{ BEFORE | AFTER } <tt class="REPLACEABLE"><i>event</i></tt>   ON <tt
class="REPLACEABLE"><i>table</i></tt>FOR EACH STATEMENT
 
</pre><br /> Emmanuel<br /><pre class="moz-signature" cols="72">-- 
Emmanuel Cecchet
Aster Data
Web: <a class="moz-txt-link-freetext" href="http://www.asterdata.com">http://www.asterdata.com</a>
</pre>