Diez B. Roggisch wrote: > But as others also already pointed out: TG doesn't impose an ORM layer on > you. > The newest 1.0.4 beta doesn't even install one anymore. Just point your app > to a DB and get happy.
One benefit of SO and SA is that they automatically add cross-database compatibility, security and performance to the database layer or your application. You need to care for all of these by yourself if you use plain SQL through a simple DBAPI module. For instance, if you build an SQL query yourself, particularly the "where" statement, you need to be very careful to not allow SQL hacking. Also, some operators in the where clause may be database dependant. If you use SA to build where clauses, you don't need to worry about that. Also, connection parameters are database dependant. If you use an ORM, you only need to exchange an URL to connect to a different database engine. Concerning performance, both SO and SA include connection pooling layers. Therefore you may still want to do go through these layers, or use an alternate connection pooling layer such as DBUtils. -- Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
