Hi
Using Python 3.7, anyone has Record Versioning working ok?
http://www.web2py.com/books/default/chapter/29/09/access-control?search=versioning#Record-versioning
Whenever I change a record under versioning, say with SQLFORM.grid(), I
will get a key error 'id'
thanks for your time,
Ben
Traceback
First of all, web2py rocks...I'm amazed how good it is :)
Record versioning is one of the great features and is working perfectly for
me except for one table. Can anyone see what the problem might be? Thanks
in advance.
Here is the definition of the table in question:
db.define_table('actions',
Hi,
I'm using web2py as a restful api, and model has record_versioning and
auth.signature enabled.
db.define_table('article',
Field('title', 'string', length=1024, required=True, unique=True),
Field('slug', 'string', length=1024, required=True, unique=True),
Field('body', 'text', req
Hi All!
I need create a report with record versioning. How to union table with
table_archive?
Thanks!
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
Yo
hi,
just wondering about record versioning on auth tables, why the table auth
events and auth cas don't have archives table when i use record versioning
on auth tables?
thanks and best regards,
stifan
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.c
Hi,
just starting out with web2py. Given a table with record versioning
enabled, I find that for every successful update operation a row will be
inserted in the archive table.
I'm using update_or_insert(), is it possible to make web2py only copy an
old row into the archive table when there's a
Hi,
i've build a (very small) standalone side project (so, running without
Web2Py) that uses the Web2Py DAL, and all goes well.
Now i'm trying to enable record versioning. but this seems not to be
working (thread._local object has no attribute 'request')
Has anybody succeeded in using record
The cascade feature should work for record versioning enabled tables?
Thanks.
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegro
Hi,
I would like to enable record versioning on an existing MySQL database in
which all tables are managed manually (migrate=False). I am concerned about
what happens if the structure of a table changes in db.define_table( ... ).
Is the associated archive table changed to match accordingly?
th
Hi,
I'm using auth.signature and db.my_table._enable_record_versioning()
to enable record versioning on a table.
db.define_table('mytable',
Field('staffid','string'),
Field('date','datetime',requires=IS_DATETIME(format='%Y-%m-%d
%H:%M:%S'), default=request.now),
Field('comment','s
Hi,
The feature of record versioning is very important to know the history of
the record.
is it possible to go back and forward (in the history)?
is it possible to merge two histories of the same (logical data), and end
up with one record ?
is it possible to have an offline application that w
something like this http://www.web2pyslices.com/slices/take_slice/35
On Tue, Jan 31, 2012 at 10:31 AM, Johann Spies wrote:
> The book describe record versioning in the Forms section (SQLFORM and
> Crud).
>
> How can I get the same when updating/deleting records through queries that
> do not use f
The book describe record versioning in the Forms section (SQLFORM and Crud).
How can I get the same when updating/deleting records through queries that
do not use forms?
Regards
Johann
--
Because experiencing your loyal love is better than life itself,
my lips will praise you. (Psalm 63:3)
Might not be a problem but the table mpn has a field with the same name mpn and
the problem goes away if the archive portion of onaccept is removed.
Hi,
I'm trying the error versioning but I'm stuck with a curious error message
and I don't see the link between what I did and this error.
A part of my Model goes like this:
db.define_table('item',
Field('ipn', 'string'),
Fie
First of all, CRUD is the hell of a productivity tool. Some findings:
1. Definiton of the archive table like given in the book:
db.define_table('mytable_arcvhive',
Field('current_record',db.mytable),
db.mytable)
breaks deletion of records in db.mytable. The foreign key constraint
in db.myt
I am trying to use versioning in an authenticated section of a
website. Instead of this:
db.define_table('my_table',
Field('saved_by',auth.user,
default=auth.user_id,update=auth.user_id,writable=False)
I was trying this:
db.define_table('my_table',
Field('saved_by','string',
default=auth
17 matches
Mail list logo