On Tuesday, January 24, 2012 10:00:52 AM Ed Leafe wrote:
> On Jan 24, 2012, at 9:53 AM, John Fabiani wrote:
> > The fix is easy as I just need to add an alias to the second (or other
> > join tables) for the primary key i.e
> > self.addField("tableName.pkid as joinpkid")
> >
> > But I wonder if it would be better and more universal to include the
> > tableName in the keys??
>
> I don't see why. It is pretty standard SQL that if you have a join that
> includes columns with the same name, you need to alias at least one of
> them. I'm frankly surprised that you are able to get a result set with two
> identically named columns.
>
>
> -- Ed Leafe
Your right !
Johnf
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/4189650.tvTpSBcQ1Z@linux-12
