"aspineux" <[EMAIL PROTECTED]> writes:
> On 18 mar, 04:20, "George Sakkis" <[EMAIL PROTECTED]> wrote:
>>
>> I'd rather avoid triggers since I may have to deal with Mysql 4. Apart
>> from that, how can a trigger know the current user ?
>
> Because each user opening an web session will login to the
On 18 mar, 04:20, "George Sakkis" <[EMAIL PROTECTED]> wrote:
> On Mar 17, 7:59 pm, "aspineux" <[EMAIL PROTECTED]> wrote:
>
> > Hi
>
> > You can get this using "triggers" and "stored procedures".
> > These are SQL engine dependent! This is available for long time with
> > postgress and only from ver
George Sakkis schrieb:
> This is more in the context of Turbogears/SQLAlchemy, but if anyone
> has implemented something similar with other packages it might be
> useful to know.
SQLObject since version 0.8 lets you define event listeners for
create/update/delete events on objects. You could hook
On Mar 17, 7:59 pm, "aspineux" <[EMAIL PROTECTED]> wrote:
> Hi
>
> You can get this using "triggers" and "stored procedures".
> These are SQL engine dependent! This is available for long time with
> postgress and only from version 5 with mysql.
> This let you write SQL code (Procedure) that will b
Hi
You can get this using "triggers" and "stored procedures".
These are SQL engine dependent! This is available for long time with
postgress and only from version 5 with mysql.
This let you write SQL code (Procedure) that will be called when
"trigged" by an event like inserting new row, updating r
