import a model ?

[Tim Richardson]

If I have a conditional model, that is a model in a folder named after its controller, how can another controller source that model?

[Anthony]

You can customize response.models_to_run.

Anthony

[Tim Richardson]

Thanks. I'm trying that but not getting it to work for me, maybe I have another problem.

The problem is a function in controller C1 which refers to a part of the model for C2. Both controllers have models in models/C1 and models/C2 

Right now I have at the top of C1

response.models_to_run['.*']  (just for debugging) but I still get a ticket saying that 

<type 'exceptions.AttributeError'> 'DAL' object has no attribute 'patient_submission'

where patient_submission is the table defined in the model models/C2/C2_db.py

I know that response.models_to_run is being changed thanks to the debugger.

--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to a topic in the Google Groups "web2py-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/web2py/OiZ6vwaNuEU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to web2py+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Tim Richardson

[Vinicius Assef]

reponse.models_to_run must be updated on models, before controller execution.

> You received this message because you are subscribed to the Google Groups
> "web2py-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an

[Anthony]

Right now I have at the top of C1

response.models_to_run['.*']  (just for debugging) but I still get a ticket saying that 

Are you saying you put that line at the top of the C1 controller? If so, that's too late -- the controller isn't run until after the models have been executed. You have to set/change response.models_to_run in one or more model files. By default:

response.models_to_run = [r'^\w+\.py$', r'^%s/\w+\.py$' % request.controller,
                          r'^%s/%s/\w+\.py$' % (request.controller, request.function)]

which sets up the standard conditional models.

Anthony

[Vinicius Assef]

An alternative would be something like this:
what_models_to_be_executed = {"C1": ["tab1.py", "tab2.py", "tab3.py"],
"C2": "tab2.py"}
response.models_to_run = what_models_to_be_executed[request.controller]

> --
> Resources:
> - http://web2py.com
> - http://web2py.com/book (Documentation)
> - http://github.com/web2py/web2py (Source code)
> - https://code.google.com/p/web2py/issues/list (Report Issues)
> ---

> You received this message because you are subscribed to the Google Groups
> "web2py-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an

[Tim Richardson]

I put it at the top of the C1 model and I know it is being executed...  I'll step through more and see what's happening

--

[Anthony]

An alternative would be something like this: 

what_models_to_be_executed = {"C1": ["tab1.py", "tab2.py", "tab3.py"],
"C2": "tab2.py"}
response.models_to_run = what_models_to_be_executed[request.controller]

Note, it must be a list (above, in the case of C2, it would just be a string).

[Anthony]

Never mind -- it does not have to be a list -- can just be a string. 

[Tim Richardson]

I have response.models_to_run = ['.*']

at the top of the C1/C1_db model.

When I put a breakpoint, it completes the rest of the C1_db model, and arrives at compileapp.py at a loop

for model in models:

 

this is the loop where the regex is evaluated.

But it doesn't enter the loop.

I'm guessing that perhaps I have reentered that loop on the last iteration of models.

Anyway, it never evaluates my new regex. 

I have been misleading with my example names: I say C1 but alphabetically the model with my response.models_to_run is actually later in the alphabet.It is the final model. The model I want to execute has alphabetic precedence.  

Perhaps this is the problem: the use of response.models_to_run does not regenerate the list of models, it just changes the test to execute a model from a candidate list, but if a candidate has already been evaluated it doesn't get looked at again. 

--

Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---

You received this message because you are subscribed to a topic in the Google Groups "web2py-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/web2py/OiZ6vwaNuEU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to web2py+un...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
Tim Richardson

[Anthony]

Oh, it looks like the issue regarding sorting of model folders was never fixed.

Massimo, can we change to sort=True in compileapp.py lines 517 and 521?

Anthony

[Tim Richardson]

 Yes, I am correct. That's a bit subtle. By making a model folder ZZZ and putting a copy of the requested model in there, it works. Not ideal. Possibly could be a bug, maybe. Or perhaps needs to be better documented. 

--
Tim Richardson

[Tim Richardson]

It doesn't seem to me to be a sort order problem. The problem seems to me to be different: the criteria for evaluating which models to execute can change while in that loop. If the criteria changes, then all candidate models (all models in other words) should be reevaluated. The loop index should reset to one. I don't know enough python yet.

[Tim Richardson]

On Friday, 4 October 2013 13:50:42 UTC+10, Tim Richardson wrote:

It doesn't seem to me to be a sort order problem. The problem seems to me to be different: the criteria for evaluating which models to execute can change while in that loop. If the criteria change, then all candidate models (all models in other words) should be reevaluated. The loop index should reset to one. I don't know enough python yet.

I don't think it's such an easy fix because it is a question of dependency resolution. 

My work around will be to put common models in a ZZZ folder 

[Tim Richardson]

https://code.google.com/p/web2py/issues/detail?id=1702

[Anthony]

I commented on the issue, but this is the intended behavior. The order of execution is fixed (though you can determine that fixed order with proper naming of files and folders) -- response.models_to_run is only intended for specification of which files get executed, not in which order. Do you have a use case where you need to dynamically change the order of model execution?

I think what you call a "workaround" (i.e., putting the model file that is common to two controllers in its own folder) is actually the cleaner design -- that model file doesn't belong to only one controller or the other, so it doesn't belong in a folder associated with only one of the controllers.

Anthony

On Friday, October 4, 2013 12:38:10 AM UTC-4, Tim Richardson wrote:

https://code.google.com/p/web2py/issues/detail?id=1702

[Anthony]

And of course, you can always put model code in a module and import it where needed.

[Tim Richardson]

Thanks. I'll try import next time.

--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to a topic in the Google Groups "web2py-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/web2py/OiZ6vwaNuEU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to web2py+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Tim Richardson

[Jonathan Lundell]

Mutatis mutandis…

You received this message because you are subscribed to the Google Groups "web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py+un...@googlegroups.com.