Some comments on the latest edits on the SQLAlchemy article. I'm not sure what this means: "*MySQL and SQLite should be using sqlalchemy.default.url, but if that fails, try sqlalchemy.url". The choice of prefixes is arbitrary. I showed both versions in the tutorial because I thought some people with one-engine apps would prefer it without the "default.". there's a comment at the bottom of the page about a change in what SQLAlchemy beta 4 accepts. There was no beta 4 when I went to sleep last night, so what happened?
I changed "import pylons; pylons.config" in the model to "from pylons import config". Ben told me earlier this would future-proof code against changes he might make later. I'm not happy with the "model." prefix throughout the Data Queries section. Some people will use this code in the model; others in the controller. I think it's less jarring to have it without the prefix and people can add it, rather than the other way around. Do others think differently? MikeB has suggested changes to the binding strategy in multi-engine apps. This has not been finalized yet, but that part of the tutorial may change. Whether to put stuff in the base controller's .__call__ method or in .__before__ or .__after__ sounds like a a bikeshed dispute. It doesn't matter on a practical level. My reason for putting it in .__call__ was to keep .__before__ and .__after__ empty in case the subclass controllers want to use them. Of course the try/finally/.remove() part has to be in the base controller since a 'try' block can't span methods. -- 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 -~----------~----~----~----~------~----~------~--~---
