On Mon, Oct 13, 2008 at 9:44 AM, Kirk Strauser <[EMAIL PROTECTED]> wrote:
> > On Thursday 09 October 2008 14:45:44 Dean Landolt wrote: > > If it's an old table, can't you just do a select distinct to get out the > > relevant data and just stick it somewhere more suitable? If there's > nothing > > else relevant there, why bother wiring SA up to it on every load? It > > couldn't be that hard to renormalize the data and put it in the place it > > belongs (wherever that is)? > > I could, but I don't want to have to re-synch it constantly. > > Yes, it would be phenomenally difficult to renormalize the data, as a > rather > large 20-year-old application runs against the current table layout. > > So, no way to trick TG/SA into using a foreign key that isn't really a > proper > foreign key? > -- > Kirk Strauser > SA lets you map to arbitrary selects -- couldn't you join to a select distinct from that groupcodes table? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
