Claudio,

> > This is absolutely required, and perhaps Jason's suggestion was directed
> > towards this. I could even accept the engine overwriting anything I
> > could have put in (so, no test for null), but it must give me back the
> > values.
>
> We can borrow the idea from MsSQL, whether good or bad: we keep the latest
> implicit generator's value retrieved in the internal request and implement a
> new item in the isc_database_info API call to get this value. Now, it's the
> responsability of the application to retrieve the latest value with the API
> call before another operation updates the latest saved value.

That looks cheap, but isn't a returning clause more flexible (whichever
way it is implemented), especially given what Jason said about the
capability already being there in the engine?
Ciao
--
____
_/\/ando