Nice. Thank you. Will commit it tonight.
On Jan 18, 1:41 pm, Tsvi Mostovicz wrote:
> Massimo,
>
> I submitted issue 625 with a patch to populate.py which allows it to take
> the compute field into consideration when populating the database.
>
> Thanks,
>
> Tsvi Mostovicz
> ttm...@gmail.comwww.lin
Massimo,
I submitted issue 625 with a patch to populate.py which allows it to take
the compute field into consideration when populating the database.
Thanks,
Tsvi Mostovicz
ttm...@gmail.com
www.linkedin.com/in/tsvim
On Mon, Jan 16, 2012 at 22:45, Anthony wrote:
> No, I don't think populate
No, I don't think populate looks at the compute attribute -- it just looks
at the field type and generates an appropriate value.
On Monday, January 16, 2012 3:21:16 PM UTC-5, tsvim wrote:
>
> Could be it works, but for populate it doesn't. I was hoping to generate a
> rule that would force popul
Could be it works, but for populate it doesn't. I was hoping to generate a
rule that would force populate to behave correctly.
For the user I can obviously deal with it in AJAX. Is it possible that
populate disregards the compute field?
Tsvi Mostovicz
ttm...@gmail.com
www.linkedin.com/in/tsvim
>
> db.define_table('accounts',
> Field('name','string'),
> Field('parent_account','reference accounts'),
> Field('account_type','string'))
>
> What I'm trying to achieve is to create a tree-like structure. So we have
> 5 "root" accounts, which can
5 matches
Mail list logo
