On 06 Apr 2014, at 2:14, Ben Hoyt wrote:
> Thanks for the info, Francisco and Alban -- that looks useful.
>
> Can you see a good way in the INSERT to combine VALUES with that nextval()
> subquery? As there are some columns that are distinct for each row, and some
> that are the same or program
Hi:
On Sun, Apr 6, 2014 at 2:14 AM, Ben Hoyt wrote:
> Thanks for the info, Francisco and Alban -- that looks useful.
May be.
> Can you see a good way in the INSERT to combine VALUES with that nextval()
> subquery? As there are some columns that are distinct for each row, and some
> that are t
Hi Adrian:
On Sun, Apr 6, 2014 at 2:30 AM, Adrian Klaver wrote:
> Still think this is something for a BEFORE INSERT TRIGGER:
I think a trigger is overkill for just a simple data-combining
procedure. JMO, but I prefere to reserve triggers for htings which
need them.
Regards.
Francisco Olarte
On 04/06/2014 05:30 AM, Francisco Olarte wrote:
Hi Adrian:
On Sun, Apr 6, 2014 at 2:30 AM, Adrian Klaver wrote:
Still think this is something for a BEFORE INSERT TRIGGER:
I think a trigger is overkill for just a simple data-combining
procedure. JMO, but I prefere to reserve triggers for hti
Hi Adrian:
On Sun, Apr 6, 2014 at 5:05 PM, Adrian Klaver wrote:
> On 04/06/2014 05:30 AM, Francisco Olarte wrote:
>> I think a trigger is overkill for just a simple data-combining
>> procedure. JMO, but I prefere to reserve triggers for htings which
>> need them.
> Well the flip side to that arg
