Also be sure to check out Elixir (which gives you SO-like model code  
but sits on top of SA):
http://elixir.ematia.de/

It's as easy to learn as SO, but you still have the power of SA under  
there if you really need to do something clever.

I've been using it since the 0.1 release and it's been a joy so far.

--i

On Mar 7, 2007, at 12:25 PM, venomous wrote:

>
> Hello,
> i have started using turbogears some days ago, now that i have a very
> basic picture of how it works i have some question.
> Basically i'm trying to switch from php to some another programming
> language for web development, and after trying some frameworks
> (probably over 10) i decided to stick with python, and i decided to
> use turbogears
> I have no problem big problems with python and turbogears in generals,
> but i feel very uncomfortable with SQLObject (and probably because i
> haven't started reading seriously the documentation ).
> Talking of reading documentation and then learn the library i would
> have a suggestion on what i should read.
> Reading on the groups and some docs, i have seen that some guys prefer
> SQLAlchemy over SQLOject (for what i have seen a lot). So considering
> that i have lost about 2 months trying frameworks, and now i want
> stick with turbogears, i would know also considering the future of
> turbogears, if the better choice is to start deploying apps using
> SQLObject or SQLAlchemy, so i don't have to read both documentation.
> Hope that doesn't sound like a fool question, but because i'm
> seriously trying to develop with turbogears and i'm spending a lot of
> time, any suggestion is much appreciated.
> Thanks in advance.
>


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to