Steve Bergman wrote: > Yes. I've been looking forward to that feature's debut in TG. Can I > also pass a dictionary to SQLObject to set the attributes of an existing > or new object to the dictionaries values? It seems like I saw somewhere > that I can already do that? Using the .set(**dict) or something like that should do the trick
> > BTW, bonono, I finally got to the reporting part of my app and tried out > the info in the link you provided me a while back to be able to do raw > SQL through SQLObject. Works great! But it did demonstrate to me how > I'd gotten used to the simplicity of SQLObject for doing simple DB > related things. (And it was a bit jarring having to switch gears even > insofar as what the fields db fields were named, e.g. "employee_phone" > vs "employeePhone".) > > A fusion of the two ways of doing things into TG would be a match made > in heaven. The only problem being that I wouldn't have anything more to > complain about! ;-) My thought too(well not the complain part ;-p). I am walking between them. Using the SQLBuilder for things of medium complexity and stored procedure on the server for hardcore SQL. SQLObject by itself is great for form filling and the like, including parent child.
