--> "maybe I could add a class method to do this in one step. "
it would be extremely nice if this was available also in the websetup without much fuss, the problems which I posted about a while back would be gone and other newbies like me wont have headaches :-) Thanks! On Jun 23, 5:12 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote: > Beachcoder: I don't know much about Exilir. Is it just a table > definer? If so, you'd create your engines/metadatas first in > SAContext and pass them to Exilir. Then you could probably use > SAContext's session management with Exilir's tables. But if Exilir > has its own session management, you'd probably want to use that > instead. Anyway, it's worth somebody experimenting with. > > On 6/23/07, voltron <[EMAIL PROTECTED]> wrote: > > > Does that mean I can instantiate an SAContext object and I can use it > > everywhere? In websetup.py, my controllers e.t.c? > > It was designed for the model, which is used by controllers. It can > be used in websetup but you may have to take a couple extra steps > since the config is available differently in websetup. If you do > CONFIG.push_process_config before using PylonsSAContext, it should > work normally. (CONFIG is changing to pylons.config in Pylons 0.9.6 > if I understand right, so the steps may change slightly.) Otherwise > you'd have to call the config-parsing methods standalone to get the > options, and then pass the options literally to the constructor. Or > maybe I could add a class method to do this in one step. > > -- > Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
