On Tuesday, May 27, 2014 8:46:19 AM UTC-4, Anthony wrote:
> I suppose we could add a setting that allows you to specify model order,
> though for backward compatibility, the initial model file (i.e., the one
> where you make that setting) would have to be first alphabetically.
>
Would it make
ation.
But to answer Henrik ... no, there's no workaround other than observing the
> naming conventions. I believe this was a design decision, although
> well before my time here.
>
Thanks for the clarification!
Henrik
>> On Wednesday, May 21, 2014 9:20:16 AM UTC-7, Henri
Anthony,
Not sure really - I was wondering if there might be a way to specify the
order of which the files would be executed.
Henrik
On Thursday, May 22, 2014 8:50:39 PM UTC-4, Anthony wrote:
>
> For now I have renamed the file to x_application.py, but this seems like
>> kind of a kludge. Is
I have a model file 'application.py' wherein I define some tables, and it
is executed before the db.py file. Thus I get the "name 'db' is not
defined" error.
For now I have renamed the file to x_application.py, but this seems like
kind of a kludge. Is there a way to work around the "alphabetic
Has this "add_button" been added to one of the recent releases? I'm
running 1.99.7 and I get
* 'SQLFORM' object has no attribute
'add_button'*
Maybe it's time to upgrade :-)
Thanks,
Henrik
On Tuesday, July 17, 2012 1:43:08 PM UTC-4, Massimo Di Pierro wrote:
>
> In trunk:
>
> form.add_but
5 matches
Mail list logo
