Bob update

[suityou01]

Does it matter which database is being used ? My solution was a general "SQL" solution which should work on any database.

Or are you saying the Insert into SELECT from query is not supported by Oracle ?

Keep digging pal.

Although in fairness couple your solution with Doodabs syntaxy thingy and you two have a solution that does indeed avoid cursors. Which as I understand from all wailing and gnashing of teeth on here is a good thing. So hats off.

[suityou01]

It is supposed to be a mighty enterprise level database so I would assume it would support standard SQL queries.

All I would say is lets wait and see what our BPM architect has to say about my solution. He has already commented that I should stick to bog cleaning which I assume was a hasty retort.

Oh no, I still see you in a white coat mopping out trap 3.

[suityou01]

The identity statement was one I use for SQL server. I assume that there would be similar for Oracle. In any case, if SY is using cursors he would still need the @DinnerId to insert into Dinner_Item table. Therefore substitute my identity statement to whatever method SY is currently using.

The debate here is for the use of cursors in a stored procedure and I have stated that for the problem that SY is facing, cursors are not required and a simple SQL statement would suffice.

Nope. This was covered in post 39.

The stored procedure debate trundles on, but we were forced into using stored procs as Oracle doesn't have an identity field, so we need to use sequences so this is all wrapped up in the insert stored proc, and the new id value returned as an output variable.

But you keep on going flower.