Thanks,
yeah, just figured I can plainly use the engine from SQLAlchemy to issue direct SQL statements (via engine.execute) without having to change anything in the setup. I know that this will certainly limit me to one DB, but I ain't going to use anything but postgresql anyways and I have full control over the project (i.e. I don't support IE, whoever wants to view the website the way it was designed needs to get firefox or live with occasional strange rendering :-) ) Uwe On Monday 28 May 2007, Dominique Eav wrote: > Uwe C. Schroeder wrote: > > Hi all, > > > > is there any "module" that allows me to get rid of SQLAlchemy/SQLObject > > and just connect to a database directly with normal DBAPI calls? > > 1. choose your db > 2. find the python module which will allow your code to communicate with > the db (for example pysqlite for sqlite, mysql-python for mysql, psycopg > or pygresql for postgres...) > 3. install the latter and use it directly to communicate with your db > > You're done ! > > That said, this ties your code to a specific db. You'll get started much > quicker if you're used to RDMS, but ORM stuff were not just designed for > fun or taste matters, you might notice one of these days. > > dom > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
