Thanks for that tip, it looks as if it will be easier than I thought to continue with the low level database routines that I know work with Firebird/ kinterbasdb.
John On 29 May, 12:26, Krys <[EMAIL PROTECTED]> wrote: > HI there, > > You don't even need a blank sqlite db if you are not planing on using > SO or SA. > > I am using TG without a DB in one app and I have used TG with just sql > strings and the low level driver. Less fun, but very easy to do. > > As a tip, I might suggest becoming aware of the turbogears.util.Bunch > class. It's a dict with foo.key style access to the key (i.e. like a > class.) This makes it easy to take the row tuples, zip them with the > column names (the keys) and turn them into class-like objects (i.e > row.col = foo). It also makes it easy to pass your objects to > templates and whatnot. > > There is nothing in TG that forces you to use any of the components > (except maybe cherrypy.) It's very flexible that way. :) > > Anyway, hope this helps. > > Krys > > On May 28, 12:59 pm, Paul Johnston <[EMAIL PROTECTED]> wrote: > > > 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 -~----------~----~----~----~------~----~------~--~---
