On Thursday, September 6, 2012 9:34:51 AM UTC-3, Massimo Di Pierro wrote:
Please open a ticket and this will be easy to fix.
Opened the ticket:
http://code.google.com/p/web2py/issues/detail?id=980
Now it was closed with status fixed, but:
-AFAIK, fileld.writable still has no effect in
Now I see what you are trying to do. I do not consider this a bug. At this
point this is the intended behavior. You want conditional computed fields
depending on user input. If a value is provided use it, if one is not
provided then compute it. That is not what compute fields were designed
I haven't followed this closely, but instead of specifying a compute
attribute for the field, could you instead specify the default attribute
as a function? In that case, the field will appear on forms -- if the user
enters a value it will be used, and otherwise the default value will be
if the user does not pass a value it will still not trigger a computation
because is not None, I think.
On Tuesday, 11 September 2012 09:17:02 UTC-5, Anthony wrote:
I haven't followed this closely, but instead of specifying a compute
attribute for the field, could you instead specify the
for that cases shouldn't use _before_insert and _before_update triggers?
--
I think so.
On Tuesday, 11 September 2012 09:42:05 UTC-5, rochacbruno wrote:
for that cases shouldn't use _before_insert and _before_update triggers?
--
Please open a ticket and this will be easy to fix.
On Wednesday, 5 September 2012 19:55:17 UTC-5, Alan Etkin wrote:
El miércoles, 5 de septiembre de 2012 12:51:06 UTC-3, Massimo Di Pierro
escribió:
yes please. Did this work in 1.99.7?
Ok, the current way is the same as in 1.99.7.
Does NOT seem to work. computed field is still not visible.
Same problem with this version: 2.0.7 (2012-09-04 18:33:19) stable (updated
with hg)
I think we should open an issue in the google code page.
--
yes please. Did this work in 1.99.7?
On Wednesday, 5 September 2012 09:07:41 UTC-5, Alan Etkin wrote:
Does NOT seem to work. computed field is still not visible.
Same problem with this version: 2.0.7 (2012-09-04 18:33:19) stable
(updated with hg)
I think we should open an issue in the
El miércoles, 5 de septiembre de 2012 12:51:06 UTC-3, Massimo Di Pierro
escribió:
yes please. Did this work in 1.99.7?
Ok, the current way is the same as in 1.99.7. SQLFORM output hides by
default computed fields.
The problem was discussed in this threads before:
I have a few fields that have compute attribute defined. I've only
inserted the records via script - compute fields are updated correctly.
I have a SQLFORM.grid which shows a join query. When I explicitly select
the computed field in the fields param - it is shown correctly.
But when I click
in your controller..
if request.args(0) == view:
db.table.field.readable = True
grid = SQLFORM.grid(.)
http://zerp.ly/rochacbruno
Em 14/08/2012 09:37, Mandar Vaze mandarv...@gmail.com escreveu:
I have a few fields that have compute attribute defined. I've only
inserted the records
I have not set readable flag during db definition. Is it set to False by
default, for compute fields ?
On Tuesday, August 14, 2012 6:16:20 PM UTC+5:30, rochacbruno wrote:
in your controller..
if request.args(0) == view:
db.table.field.readable = True
grid = SQLFORM.grid(.)
Does
13 matches
Mail list logo
