On 2 Jul, 20:00, Christopher Arndt <[EMAIL PROTECTED]> wrote:
> jrpfinch schrieb:
>
> >> Hmmm, you might also try changing:
>
> >> ne_ems_id = ForeignKey("Ems_live")
>
> >> to:
>
> >> ne_ems = ForeignKey("Ems_live")
>
> > Unfortunately I can't change ne_ems_id to ne_ems because I have not
> > control over the structure of the underlying database
>
> No, that doesn't mean that the column name in the underlying database
> will be 'ne_ems'. SQLObject will build the right column name with some
> name-mangling magic automatically. Just try it out.
>
> For details please read the SQLAlchemy docs. There are also ways to
> influence how this name-mangling actually works, but again, you have to
> check the SO docs for that.
>
> Then again, if you need full control over the column names in the
> database, SQLAlchemy will probably work better for you.
>
> Chris
dir(b) in the tg-admin shell, a bit of trial and error and i've
discovered that the following works:
b.ne_ems_.ems_name
I'll take a look in the SO docs but if anyone knows how I could
influence this name-mangling without editing the underlying database,
I would be very grateful
thank you Kevin and Chris
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
