[web2py] Re: Database compute fields

2014-04-14 Thread horridohobbyist
Are you saying I have to update the price field, regardless of whether it has changed or not?? That's not very logical. On Sunday, 13 April 2014 18:39:51 UTC-4, Anthony wrote: > > I believe you have to provide the price field in your update as well. -- Resources: - http://web2py.com - http://w

[web2py] Re: Database compute fields

2014-04-14 Thread Anthony
Yes, otherwise the DAL would have to do a db query to retrieve all the records being updated and issue a separate update for each record (since they may not all have the same price value and therefore might require different updated values in the computed field). On Monday, April 14, 2014 7:09:

[web2py] Re: Database compute fields

2014-04-14 Thread horridohobbyist
Sonovagun, you're right! But that rather diminishes the usefulness of 'compute', IMO. On Monday, 14 April 2014 08:15:14 UTC-4, Anthony wrote: > > Yes, otherwise the DAL would have to do a db query to retrieve all the > records being updated and issue a separate update for each record (since >

[web2py] Re: Database compute fields

2014-04-14 Thread Anthony
On Monday, April 14, 2014 11:10:28 AM UTC-4, horridohobbyist wrote: > > Sonovagun, you're right! But that rather diminishes the usefulness of > 'compute', IMO. > Yes, though I suppose the alternative would add a lot of complexity (and potentially inefficiency). Maybe at least when .update_record