> It is barID, not bazID - the name is derived from the name being assigned to. > > Despite being, now, understandable, the fact that this differs from standard > behavior of other columns both confuses, and infuriates, like the alien > concept of 'wuv'. Sure, it's good to identify differences, but I -know- how > I programmed my model definition. I don't need SO "helping" me. > > Thanks, though, as your example put me on the right track! My code now > works. > (Apparently SO doesn't like mixing strings and magical .q. variables. The > SQL was very messed up in my example code.)
You're right, although knowing that it's barID makes a certain amount of sense.. just not loads. I think I can see why they did it, although there could be more (read: any) documentation on .q.* . -Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
