I'm doing it form the application layer and I don't think it can be
done in the database layer, how the trigger will figure out which user
is doing the query?, It's the same problem you are trying to solve!
Duh! That is what happens when you start having high levels of caffeinne in your blood and haven't had a good night sleep... thanks for putting me on the track again.
I will study Tim's approach more. This thing got more complicated than I thought it would be. At least I'm learning more about PostgreSQL internal architecture.
Thank you for your help.
Marcelo.
On 4/25/07, Manuel Sugawara <masm@fciencias.unam.mx> wrote: "Marcelo de Moraes Serpa" <celoserpa@gmail.com> writes:
> Hi Manuel,
>
>> each time the user sends a request I do more or less the following:
>
> Could a trigger be used to implement this ? Or are you doing this from the
> application layer?
I'm doing it form the application layer and I don't think it can be
done in the database layer, how the trigger will figure out which user
is doing the query?, It's the same problem you are trying to solve!
> My problem is that, like Til, I don't have full control over my
> request cycle as I'm over a very high-level framework (Actually it
> is an data-oriented application generator, called GeneXus).
Maybe you can use Til approach with temporal tables.
Regards,
Manuel.
