Michael Bayer wrote: > im not exactly sure why Jonathan thinks that the "url" forces one > to "define my connection up front". if youre saying, "i want to > distribute the application without an .ini file" thats fine...but when > the thing is actually *used*, there will be an .ini file or other > configuration defined when things run. if you want to define your > model independently of connection, just use an empty MetaData. Set > up the SAContext to bind the engine or individual connections to the > session instead...or give it your MetaData for it to bind when youre > ready. theres really nothing to it.
I just didn't like having my model get its URI directly from the Pylons config, for the reasons I stated previously. However, you just solved my issue :) I had no idea that I was able to do this with SAContext, and effectively use it just as I want to. Thanks for the explanation Mike! -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
