Archives of the TeradataForum

Message Posted: Tue, 08 Apr 2014 @ 22:02:16 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Dieter Noeth wrote :

Ahh, that might well explain the problem, although it does seem a sorry situation when two PE's working against the same Table can't even manage values into a Column without tripping over each other .... because either that's what they were doing or there's a bug in the software (which is actually my suspicion).

Anyway, yet again Dieter, you bring clarity to a situation ... thank you.

As to what I'm doing, it's simply a case of generating an artificial key to a Table - and the Table itself won't be big anyway - so I'll simply get around it by doing a Select Max on the Column, add 1 to it, then use that for the next value. ?

This will be fine, as the adding of the row will be single streamed via a Teradata Queue process (using another one of your ideas, by the way - remember, the high value entry into the Queue to stop it ?)

By the way, loving the concept of Arrays ?.... it does seem as though Teradata is at last catching up with Oracle on SQL functions which, I'm sure you would agree, is about time.

In my view, what they now need to enhance is ?:-

1. SQL Functions (enabling Loops)

2. Ability to create local Functions within a Stored Procedure

ttfn

Regards

David Clough
Senior BI Database Designer
BI Competency Centre

	<Prev	Next>		<<First	<Prev	Next>	Last>>