Sergio H. Gonzalez ha scritto:

> From: "Fulvio Senore"
>
>> What about storing the IDs in memory instead of writing them to a
>> temporary table?
>>
>
> Hi Fulvio, thanks for the reply, but I'd like the DB to "know" what the selected
> fields are. Because I'm looking for a general solution and in some cases I use
> the selected fields in a stored procedure. And sometimes a selected record
> implies that other users can't select it until the first user commit or
> rollback. That would be the case for selected invoices when I'm doing a payment.
> The second user can't select the same invoice unless the first user cancel the
> operation (the payment)
>

If I remember it correctly data in temporary tables are only visible to
the user that stored them. Other users cannot see them: for that reason
they are rather equivalent to storing data in memory.

If you want another user to know if you have selected an invoice you
cannot use temporary tables, I think.
You will have to use a normal table and make sure that rows are deleted
when the application exits.

It looks like looking for troubles to me. Maybe you can find a better
design: for example, having two people working at invoice payment at the
same moment is a rather strange situation. Usually only one user works
at a similar job, unless your customer is a really large one.

Fulvio Senore