> Eh, also, I think that there has to be some way to get the value
> back to the client. :)

What I would like to see (and I believe the capability exists at the BLR
level due to conversations I have had with Charlie Caro) is for there to be
SYNTAX similar to a stored procedure which can return a single row, have an
INSERT statement which can return the values of the record just inserted.

e.g.

INSERT INTO ATABLE( ACOL2, ACOL3 )
VALUES ( :col2val, :col3val )
RETURNING ( ACOL1 )
INTO ( :col1val );

With this capability it would be possible to pull back from the server
values of columns potentially affected in trigger operations. If Col1 were a
trigger maintaned column to give a PK value then its value would come back
to the client along with the packet indicating success (no more overhead in
most cases) and the client would stay in sync much more easily. IBO folks
could kiss GeneratorLinks entries good bye which would make things a lot
more efficient.

This would be more difficult to accomplish with UPDATE but if you did use
the RETURNING feature, it could enforce that only a single row were updated.
Which is also a good thing.

For this feature to be added, I would immediately make IBO able to take
advantage of such a great boon!

Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com