John, You don't have to use SQLObject or SQLAlchemy. If you'd rather not, you can point TurboGears at a blank SQLite database, and do all you database work by hand. It's your call.
Personally, I find SQLAlchemy very helpful and a lot better than writing raw SQL. As for the limited Firebird support, well, you may have to dive into the source code and fix some bugs yourself. It's not as well supported as other databases. Paul johnbraduk wrote: >I am starting out with TG trying to interface to an existing Firebird >database. I really like the way TG brings everything together. >However I have fallen out of love with the database side of it. I >must be missing something as I don't understand why I am forced to >use SQLObject or SQLAlchemy. The documentaion says the SQLObject has >to have a unique numeric key, which means that I must modify all my >existing tables and SQLAlchemy will not connect at all to my Firebird >databases (I have tried the udated firebird.py). I am fully aware of >how to read and write records via native sql and kinterbasdb so what >is the advantage of having to learn 2 non-intuitive ways of >interfacing to a database? These two SQL modules seem to be an >enormous overhead and complication just to make it more "pythonic" > > >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
