Thanks. Will check that out.
On Friday, July 13, 2012 7:10:49 PM UTC-4, Massimo Di Pierro wrote:
>
> You need web2py trunk.
>
>
> On Friday, 13 July 2012 16:07:18 UTC-5, DJ wrote:
>>
>> Hello,
>>
>> I have been trying to get auditing to work but run into the error below.
>> W2P version: 1.99.7 /
You need web2py trunk.
On Friday, 13 July 2012 16:07:18 UTC-5, DJ wrote:
>
> Hello,
>
> I have been trying to get auditing to work but run into the error below.
> W2P version: 1.99.7 / Mysql 5.0
>
> Any recommendations on how to fix this?
>
>
> 1.
> 2.
> 3.
> 4.
> 5.
> 6.
> 7.
>
> Traceback (m
Hello,
I have been trying to get auditing to work but run into the error below.
W2P version: 1.99.7 / Mysql 5.0
Any recommendations on how to fix this?
1.
2.
3.
4.
5.
6.
7.
Traceback (most recent call last):
File "/home/www-data/web2py/gluon/restricted.py", line 205, in restricted
exe
On Wednesday, July 4, 2012 2:23:16 PM UTC-4, Massimo Di Pierro wrote:
>
> web2py has change since one year ago. Now you simply do:
>
>db.define_table('mytable',fields...,auth.signature)
>... define more table ...
>auth.enable_record_versioning(db)
>
> and mytable will have a mytable
Hello Joel,
web2py has change since one year ago. Now you simply do:
db.define_table('mytable',fields...,auth.signature)
... define more table ...
auth.enable_record_versioning(db)
and mytable will have a mytable_archive that works as Nick suggested.
On Tuesday, 3 July 2012 16:15:2
Hi Nick Name,
Did you ever find a solution that met all your requirements? What you've
described is exactly what I am facing now.
Joel
On Friday, May 6, 2011 6:18:49 PM UTC-4, nick name wrote:
>
> My use of web2py requires an audit trail for (essentially) all database
> tables; The preferable
I don't know if there would be a good way to do this with any DAL/ORM. The
best and most reliable way to handle this (and I hate to say it) might be
using triggers in your database server. So that any change would trigger an
audit action by the SQL server, which would write the change to an audi
Thanks for the answer. However, as I mentioned in my original post, the
crud's record versioning is not sufficient for my needs.
On Friday, May 6, 2011 6:44:18 PM UTC-4, pbreit wrote:
>
> Check out "auth.signature". It adds and manipulates these columns:
> is_active, created_on, created_by, modified_on, modified_by.
>
Thank you for your answer. This is a good "mix-in" table for the things I
need. However, neither signatu
Have a look at http://web2py.com/book/default/chapter/07#Record-Versioning
On May 6, 6:18 pm, nick name wrote:
> My use of web2py requires an audit trail for (essentially) all database
> tables; The preferable way to do that is to keep a "foo_history" table for
> each table "foo". The records (
Check out "auth.signature". It adds and manipulates these columns:
is_active, created_on, created_by, modified_on, modified_by. I think
is_active is to be used in place of deleting but I'm not sure. I believe
it's based on the Table Inheritance
capability: http://web2py.com/book/default/chapter
11 matches
Mail list logo
