Of course, silly me. Couldn't see the trees for the forest :-) Thank you
Anthony.
Chris
On Thu, Apr 19, 2012 at 1:20 AM, Anthony wrote:
> db.property.property_type.writable = False
>
> Anthony
>
>
> On Wednesday, April 18, 2012 4:32:02 PM UTC-4, leftcase wrote:
>>
>> I've put this into the cont
db.property.property_type.writable = False
Anthony
On Wednesday, April 18, 2012 4:32:02 PM UTC-4, leftcase wrote:
>
> I've put this into the controller to test this out:
>
> def create_newbuild():
> #newbuild and resale properties share the same table.
> #the extraneous fields are rendere
I've put this into the controller to test this out:
def create_newbuild():
#newbuild and resale properties share the same table.
#the extraneous fields are rendered non-writable by the below
db.property.land.writable = False
db.property.reference_number.writable = False
db.prop
Thanks for confirming this for me, this did seem to be the most sensible
way to approach the problem :-)
Chris
On Wed, Apr 18, 2012 at 1:04 AM, simon wrote:
> You can do this with a single form. At the top of the controller set
> readable=false, writable=false for the fields you do not want on
You can do this with a single form. At the top of the controller set
readable=false, writable=false for the fields you do not want on the form.
On Tuesday, 17 April 2012 23:44:54 UTC+1, leftcase wrote:
> I'm a new adopter of web2py and I'm trying to learn the framework by
> building a simple p
if you need to "do" common operation with the two "sets" (old and new),
create a table that maps the "larger" (as in "attributes") set and leave
for the other set the fields not relevant to NULL.
In your case, if "old" table has more columns, just insert the values from
"new" leaving all the non
6 matches
Mail list logo
