Hi,

>At 01:52 PM 21-11-01 +0100, Martijn Tonies wrote:
>> >On 20 Nov 2001, at 17:49, Jason Wharton wrote:
>
>> >> > I would like to see an AUTOINC field type, the engine would
>> >> As long as you make the trigger so it only puts in a value if it is
>> >> NULL would this be a useful mechanism.
>
>> >Good point Jason, yeah it should only be if the field is NULL going
>> >in. The idea is that I have definitions for about 50 tables at this
>> >point, and doing a copy and paste of the same trigger code, is
>> >getting a boring, plus it's error prone, so I thought it's the kind of
>
>>Eh, also, I think that there has to be some way to get the value back to

the

>>client. :)

>And..Ugh, just think what problems there would be in our comfortable little

world if that >AUTOINC type were under transaction control...

>Helen

Eh, more ugh... Personally, I hate autoinc fields - but people really seem
to use them :)

And IF they get implemented, you really need to be able to get the value at
the client. And I think that one issue indeed would be that it's a
non-broken sequence... Or perhaps not? That would be a lot easier I guess :)


Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com


[Non-text portions of this message have been removed]