Hi,
I think you'd better reference your store_registration table once by id in
the temperature table.
Field('store_registration_id', 'reference store_registration', writable=
False),
In that way you comply with the rule of single_point-of_definition. The way
you define your temperatures
table, when a user updates his contact_number it has to cascade to the
temperatures table.
What you want can be achieved by 'reference store_registration' you could
remove the reference and
replace it with an IS_IN_DB() validator for instance for Cell_No:
IS_IN_DB(db, 'store_registration.contact_number', '%(contact_number)s')
and then write your own ON UPDATE CACADE functions
Kind regards,
Annet
--
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)
---
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/web2py/0b0dd14b-9e77-4df2-8ce0-58a00baf0c79o%40googlegroups.com.
