Sent from my iPhone
Please excuse any typos ;)
On Jan 22, 2008, at 9:11 AM, walterbyrd <[EMAIL PROTECTED]> wrote:
>
> On Jan 22, 2:33 am, Dmitry Lipovoi <[EMAIL PROTECTED]> wrote:
>> orm is abstraction over database query language. you can make queries
>> in oo-terms. so your business logic stays clear and you dont care
>> about object persistence.
>>
>> also with orm you can change backend (from MySQL to Postgre for ex.)
>> just
>> by edit config. if you work with native sql its not always possible.
>>
>
> True. But as I understand it, using an ORM means you take a
> performance hit. I wonder just how much it will affect performance to
> use SQLAlchemy?
Thus is part of why I an interested in this approach, but don't want
to loose all if the advantages oh SA.
I have no need for switching databases for this project and if I
Did I have all SQL and connection string in one conf file so it would
be very easy to alter.... I have no need for SA's object syntax for
queries, I have most my SQL aleady defined from a previous version of
the project. The same goes for ORM in this case.
I do however need a model to seperate my logic out, plus the rest of
pylons is perfect for my needs.
I guess I am looking for best practices for a pylons model when not
using SA.
Thanks for all the help
- 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
-~----------~----~----~----~------~----~------~--~---
