On Tue, 2006-07-11 at 07:04 -0800, percious wrote: > For what it's worth, I recommend starting with SQLAlchemy and Kid. > Right now there is not stellar support for Genshi, especially with > respect to the templates used in TG Widgets (I know this is changing) > The good news is that if you write your templates using Kid they will > be most likely Genshi compliant. > > We went down the SO road because that's all that was available back > then. The limitations of SO became apparent in the last few weeks, and > I am spending over 2 weeks getting our stuff converted over to SA. SA > is TONS more versatile and does exactly what I want out of an > database-object mapper, so I recommend using that. Activemapper or > TurboEntity will get you quickly up and running, and both should work > with brute-force SA tables/mappers.
Thanks for the tips. The pros of SO that I can see is simplicity and documentation. But this projects third phase has me seriously expecting to hit walls with any kind of simple database, one of my main reasons for looking here. I was thinking of Django with SA, and then started to wonder why I would want Django at all if I was going with SA. ( The answer is that admin. but for this client, I think the hard stuff that will be easier with SA is going to outweigh the ease of the django admin ). Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
