Sent from my iPhone
Please excuse any typos ;)
On Jan 22, 2008, at 3:09 AM, "Antoine" <[EMAIL PROTECTED]> wrote:
>
>
>> I am a little unsure of the Model concepts though, and how tightly
>> they are bound to SQLAlchemy.
>
> They aren't. Actually, it seems you are not even obliged to use a
> Model at
> all. You can just write controllers and handle all the logic inside
> them
> if you want (although many people would probably recommend against
> this
> :-)).
I should have mentioned I am not at all new to MVC or ORM, use them
both in java apps often.
I would always use a model unless maybe if there was no db.
>
>
>> In general it seems like a lot of configuration to make simple SQL
>> queries.
>
> Some of that configuration (the table declarations) replaces hand-
> written
> CREATE TABLE queries, though, and in a more portable way.
So if I didnt need the portable scheme creation, can I just skip the
table def in the model?
Also if I don't plan on ORM, I wouldn't need the object map at all
correct?
>
>
> Also, SQLAlchemy gives you transparent connection pooling, and other
> goodies.
>
Can I use direct queries with engine.execute("select * from") and
still take advantage of the goodies?
I am interested in all pylons and sqlalch have to offer, but am
exploring all options, as I'll likely want ORM on case by case basis
and would want to skip the extra conf stuff if not needed.
Thanks,
- kevin
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
